- collaboration
- Invite Team Members
- Assign Projects
- Users & Role Management
- Review Management [Test Cases]
- Review Management [Elements]
- Execution Controls
- Manage Test Cases
- Test Case List Actions
- Import and Export Test Cases
- Import Test Project Test Cases
- Importing Postman Collections and Environments
- Update Test Case result in a Test Plan
- Test Cases (Mobile Web App)
- Test Step Types
- Type: Natural Language
- Type: REST API
- Type: Step Group
- Type: For Loop
- Type: While Loop
- Type: Block
- Type: If Condition
- Nested Step Groups
- Image Injection
- Cross-application testing
- Test Data Types
- Raw
- Parameter
- Runtime
- Random
- Data Generator
- Phone Number
- Mail Box
- Environment
- Concat Test Data
- Create Test Data [Parameter]
- Update Test Data Profile
- Updating Value in TDP
- Import TDP
- Bulk Deletion of a Test Data Profile
- Create Test Data [Environment]
- Elements (Objects)
- Web Applications
- Record Single Element
- Record Multiple Elements
- Create Elements
- Supported Locator Types
- Formulating Elements
- Shadow DOM Elements
- Verifying elements in Chrome DevTools
- Handling iframe Elements?
- Dynamic Locators using Parameter
- Dynamic Locators using Runtime
- Using Environment Test Data for Dynamic Locators
- Locating Dynamic Elements in Date Widget
- Freeze & Inspect Dynamic Elements (WebPage)
- Locating Dynamic Elements in Tables
- Import/Export Elements
- AI Enabled Auto-Healing
- Locator Precedence (Web Apps)
- Verify Elements from Test Recorder
- test step recorder
- Install Chrome Extension
- Install Firefox Extension
- Install Edge Extension
- Exclude Attributes/Classes
- test plans
- Add, Edit, Delete Test Machines
- Add, Edit, Delete Test Suites
- Schedule Test Plans
- Run Test Suites In Parallel
- Cross Browser Testing
- Distributed Testing
- Headless Testing
- Test Lab Types
- Disabling Test Cases in Test Plans
- AfterTest Case
- Post Plan Hook
- AfterTest Suite
- Email Configuration in Test Plan
- Execute Partial Test Plans via API
- Ad-hoc Run
- Test Plan Executions
- Dry Runs on Local Devices
- Run Tests on Private Grid
- Run Tests on Vendor Platforms
- Run Test Plans on Local Devices
- Test Locally Hosted Applications
- Debug Test Case Failures
- Parallel and Allowed queues
- debugging
- Debug results on local devices (Web applications)
- Debug Results on Local Devices
- Launch Debugger in the Same Window
- Testsigma Agent
- Pre-requisites
- Setup: Windows, Mac, Linux
- Setup: Android Local Devices
- Setting up iOS Local Devices
- Update Agent Manually
- Update Drivers Manually
- Delete Corrupted Agent
- Delete Agents: Soft & Permanent
- Triggering Tests on Local Devices
- troubleshooting
- Agent - Startup and Registration Errors
- Agent Logs
- Upgrade Testsigma Agent Automatically
- Specify Max Sessions for Agents
- Testsigma Agent - FAQs
- continuous integration
- Test Plan Details
- REST API (Generic)
- Jenkins
- Azure DevOps
- AWS DevOps
- AWS Lambda
- Circle CI
- Bamboo CI
- Travis CI
- CodeShip CI
- Shell Script(Generic)
- Bitrise CI
- GitHub CICD
- Bitbucket CICD
- GitLab CI/CD
- desired capabilities
- Most Common Desired Capabilities
- Browser Console Debug Logs
- Geolocation Emulation
- Bypass Unsafe Download Prompt
- Geolocation for Chrome & Firefox
- Custom User Profile in Chrome
- Emulate Mobile Devices (Chrome)
- Add Chrome Extension
- Network Throttling
- Network Logs
- Biometric Authentication
- Enable App Resigning in iOS
- Enable Capturing Screenshots (Android & iOS)
- Configure Android WebViews
- Incognito/Private mode
- Set Google Play Store Credentials
- addons
- What is an Addon?
- Addons Community Marketplace
- Install Community Addon
- Prerequisites(Create/Update Addon)
- Create an Addon
- Update Addon
- Addon Types
- Create a Post Plan Hook add-on in Testsigma
- Create OCR Text Extraction Addon
- configuration
- API Keys
- Security(SSO)
- Setting Up Google Single Sign-On(SSO) Login in Testsigma
- Setting Up Okta Single Sign-On Integration with SAML Login in Testsigma
- Setting up SAML-based SSO login for Testsigma in Azure
- iOS Settings
- Creating WDA File for iOS App Testing
- uploads
- Upload Files
- Upload Android and iOS Apps
- How to generate mobile builds for Android/iOS applications?
- Testsigma REST APIs
- Environments
- Elements
- Test Plans
- Upload Files
- Get Project Wide Information
- Upload & Update Test Data Profile
- Fetch Test Results (All Levels)
- Trigger Multiple Test Plans
- Trigger Test Plans Remotely & Wait Until Completion
- Run the Same Test Plan Multiple Times in Parallel
- Schedule, Update & Delete a Test Plan Using API
- Update Test Case Results Using API
- Create and update values of Test Data Profile using REST API
- Rerun Test Cases from Run Results using API
- open source dev environment setup
- macOS and IntelliJ Community Edition
- macOS and IntelliJ Ultimate Edition
- Windows and IntelliJ Ultimate Edition
- Setup Dev Environment [Addons]
- NLPs
- Retrieve Value in Text Element
- Capture Dropdown Elements
- Unable to Select Radiobutton
- Unable to Click Checkbox
- Clearing the Session or Cookies
- UI Identifier NLP
- Drag & Drop NLP
- Uploading Files NLP
- setup
- Server Docker Deployment Errors
- Secured Business Application Support
- Troubleshooting Restricted Access to Testsigma
- Why mobile device not displayed in Testsigma Mobile Test Recorder?
- Unable to Create New Test Session
- Agent Startup Failure Due to Used Ports
- Tests Permanently Queued in Local Executions
- Fix Testsigma Agent Registration Failures
- Testsigma Agent Cleanup
- Need of Apache Tomcat for Testsigma Agent
- web apps
- URL not accessible
- Test Queued for a Long Time
- Issues with UI Identifiers
- Missing Elements in Recorder
- Collecting HAR File
- Errors with Browser Session
- Page Loading Issues
- mobile apps
- Failed to Start Mobile Test Recorder
- Troubleshooting “Failed to perform action Mobile Test Recorder” error
- Test Execution State is Queued for a Long Time
- Mobile app keeps stopping after successful launch
- More pre-requisite settings
- Unable to start WDA Process on iPhone
- Most Common causes for Click/Tap NLP failure
- Finding App Package & App Activity (Android)
- Cross-environment Compatible ID Locators (Android)
- Why Accessibility IDs Over other Locators?
- Common Android Issues & Proposed Solutions
- Finding the App Bundle ID for iOS
- on premise setup
- On-Premise Setup Prerequisites
- On-Premise Setup with Docker-compose File
- Post-Installation Checklist for On-Premise Setup
- Install Docker on an Unix OS in Azure Infrastructure
- SMTP Configuration in Testsigma
- Configure Custom Domains
- salesforce testing
- Intro: Testsigma for Salesforce Testing
- Creating a Connected App
- Creating a Salesforce Project
- Creating Metadata Connections
- Adding User Connections
- Build Test Cases: Manual+Live
- Salesforce Element Repositories
- Intro: Testsigma Special NLPs
- Error Handling On Metadata Refresh
- Automating Listview Table NLPs
- windows automation
- Intro: Windows Desktop Automation
- Windows (Adv) Project & Application
- Object Learning (Using UFT One)
- Converting TSR Files to TSRx
- Importing/Updating TSRx Files
- Test Cases for Windows Automation
- Error Handling Post TSRx File Update
Body Data
Adding body data in RESTful API testing is the process of sending additional data to the server in the body of the request. You will need to send body data with requests whenever you need to add or update structured data. For example, if you're sending a request to add a new customer to a database, you might include the customer details in JSON. Typically, you will use body data with PUT, POST, and PATCH requests.
A payload within a GET request message has no defined semantics. Sending a payload body on a GET request might cause some existing implementations to reject the request.
The Body tab in Testsigma allows you to specify the data you need to send with a request. You can send various types of body data to suit your API.
None Body Data
By default, Testsigma will select None - leave it selected if you don't need to send a body with your request.
Form-data
Data from website forms is frequently sent as multipart/ form-data to APIs.
- Navigate to Body > form-data tab. Form data allows you to send key-value pairs and specify the content type. In the value field, you can enter plain text or replace it with the test data type or you can enter file path, for example @"/Users/Downloads/Sample Attachment File.pdf".
- Hover over the key field to select text or a file. If you choose a file, you can upload it in the Value field.
- You can attach files using form-data. When you repeatedly make API calls that send duplicate files, Testsigma will persist your file paths for later use.
- This also helps you run collections that contain requests requiring file uploads. Uploading multiple files, each with its content type, isn't supported. Once your data and other request details are set up, select Update to run your request.
URL-encoded
URL-encoded data uses the same encoding as URL parameters. Suppose your API requires URL -encoded data. Select x-www-form-url-encoded in the Body tab of your request. Enter your key-value pairs to send with the request, and Testsigma will encode them before sending. In the value field, you can enter values by test data type. Once your value and other request details are set up, select Create to run your request.
Binary
Binary data is data that is not composed of text characters. It is typically encoded in binary formats such as images, audio, and video. This can be done by sending a request with the binary data and then verifying that the response contains the expected data. You can run your request by uploading the file and clicking Create.
Raw
You can use raw body data to send anything you can enter as a node and value. In the value field, you can enter values by test data type. Use the raw tab and the type dropdown list to indicate your data format (JSON, text, or XML), and Testsigma will enable syntax highlighting and append the relevant headers to your request. Once your raw and other request details are set up, select Create to run your request.
GraphQL
GraphQL enables you to communicate and execute queries using pre-existing data. The query language of GraphQL assists APIs in retrieving and providing data. GraphQL APIs simplify data gathering than REST APIs by providing all necessary data in one clear structure.
- To test APIs using GraphQL queries, navigate to API Request > Body > GraphQL.
-
After you select GraphQL, you will see two sections: Query and Variables, as shown in the image above. Now, enter your GraphQL Query into the Query field.
NOTE:When selecting GraphQL, the request method is by default, set to POST.
-
After entering the query, you can enhance query flexibility by adding variables. You can define these variables in either JSON format or using the Table option in the Variables section.
NOTE:You can optionally use variables in GraphQL.
- When adding variables in JSON format, enter keys and variables in the form { "code": "US" }.
- Alternatively, when you select the Table format for adding variables, you can conveniently select Keys from a dropdown menu and provide corresponding Values. You can include Test Data (Parameter, Environment, Runtime) in the Value section of the table to try out different scenarios with different variable values.
- Click Send button to initiate the request once you have set up the queries and variables. This action will result in a JSON Response.
- Finally, you can Store Variables or Add Verification for validation after generating the JSON Response. The specified test data values will trigger corresponding responses during the execution of test cases.