- collaboration
- Invite Team Members
- Assign Projects
- Users & Role Management
- Review Management [Test Cases]
- Review Management [Elements]
- Execution Controls
- test cases
- Test Cases
- Test Case List Actions
- Import and Export Test Cases
- Import Test Project Test Cases
- Importing Postman Collections and Environments
- Test cases for Desktop Windows
- Update Test Case result in a Test Plan
- Test cases for Mobile Web Application
- 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
- Create Test Steps
- 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 Multiple Elements
- Record Single Element
- 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
- Import/Export Elements
- AI Enabled Auto-Healing
- 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 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
- Triggering Tests on Local Devices
- troubleshooting
- Agent - Startup and Registration Errors
- Fetching Agent logs
- Upgrade Testsigma Agent Automatically
- 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 and update test data profile
- Trigger Multiple Test Plans
- Trigger Test Plan remotely and wait until Completion
- Run the same Test Plan multiple times in Parallel
- Schedule, Update and 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
- Unable to retrieve value stored in text element
- Unable to capture dropdown element
- Unable to Select Radiobutton
- Unable to Click Checkbox
- 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 due to unexpected error
- web apps
- URL not accessible
- Test Queued for a Long Time
- Issues with UI Identifiers
- Missing Elements in Recorder
- Collecting HAR File
- 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)
- 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
Rerun Test Cases from Run Results using API
In Testsigma, you can re-run the test cases from a test run result using API. This article discusses how to rerun failed test cases, all test cases, or custom test cases from a particular test run result using REST API.
Test Case Execution details using REST API
This endpoint allows users to get details of all Test case executions using REST API.
Request Type | GET |
---|---|
Endpoint | https://app.testsigma.com/api/v1/execution_results/986/test_case_results |
Authorization | Bearer <API_Token> Same as the Testsigma API key mentioned above. |
Request Body | { |
Request fields
executionId: Execution ID of Test Plan
executionResultId: Result ID of Test Plan Execution
testCaseId: ID of Test Case
testCaseResultId: ID of Test Case result
iterationResultId: ID of iteration result
testSuiteId: ID of Test Suite
testSuiteResultId: ID of Test Suite result
Trigger Rerun using REST API
This endpoint allows users to trigger the rerun of selected test cases using REST API.
Request Type | POST |
---|---|
Endpoint | https://app.testsigma.com/api/v1/execution_results |
Authorization | Bearer <API_Token> Same as the Testsigma API key mentioned above. |
Request Body | { |
Response Body | { |
If your test case is data-driven, and you need to add iterations, you need to send a different payload. Refer to the sample payload below:
{
"executionId": 325,
"executionResultId": 473,
"isReRun": true,
"reRunType": "USER_PICKED",
"testCaseResultRequests": [
{
"id": 2915,
"iterationReRunType":"USER_PICKED",
"iterationResultIds": [
2916, 2917
]
}
]
}
Request fields
executionId: Test Plan Execution ID
executionResultId: Test Plan Execution result ID
reRunType: Test cases you want to rerun - "ALL_TESTS / ONLY_FAILED_TESTS / ALL_ITERATIONS / ONLY_FAILED_ITERATIONS/ USER_PICKED"
iterationReRunType: Iterations you want to rerun - “ALL/FAILED/PASSED/USER_PICKED"
Response fields
Id: ID of the Test Plan Result
Execution: The Test Plan details are located within the nested Execution JSON Object including the Test Plan ID as "id," Application Version ID as "applicationVersionId," Test Plan name as "name," Test Plan Description as "description" and so on.
result: Result Status of the Test Plan - QUEUED, PASSED, FAILED, ABORTED, or STOPPED
status: Current Status of the Test Plan creation - STATUS_CREATED
executedBy: ID of the executor
buildNo: Build Number specified in the Test Plan Trigger call
isVisuallyPassed: Whether visual testing passed or not. True or False.
environment: Environment parameter selected for the Test Plan
triggeredType: Triggered type for the Test Plan whether by API or via Testsigma App
totalRunningCount: Total number of running tests
page_timeout: Global Page load timeout in seconds
element_timeout: Global Element load timeout in seconds
recovery_action: Action to be performed on test failure - "Run_Next_Testcase"
onaborted\action: Action to be performed on test abort - "Reuse_Session"
screenshot_option: When to take screenshots - "FAILED_STEPS", “ALL_STEPS”, “NONE”
group_prerequisite_fail: Action to perform on Test Suite prerequisite failure
test_case_prerequisite_fail: Action to perform on Test Case prerequisite failure
test_step_prerequisite_fail: Action to perform on Test Step prerequisite failure
totalQueuedCount: Total number of queued tests
Stop Rerun using REST API
This endpoint allows users to stop the rerun of already executed test cases using REST API.
Request Type | PUT |
---|---|
Endpoint | https://app.testsigma.com/api/v1/execution_results |
Authorization | Bearer <API_Token> Same as the Testsigma API key mentioned above. |
Request Body | { |
Response Body | { |
If you want to stop only one execution run instead, you need to pass "canStopAll": false. By default, it is true.
Request fields
canStopAll: "true” if you want to stop all executions. “false” if you want to stop only some executions.
result: Result of Execution.
Response fields
Id: ID of the Test Plan Result
Execution: The Test Plan details are located within the nested Execution JSON Object including the Test Plan ID as "id", Application Version ID as "applicationVersionId", Test Plan name as "name", Test Plan Description as "description" and so on.
result: Result Status of the Test Plan - QUEUED, PASSED, FAILED, ABORTED, or STOPPED
status: Current Status of the Test Plan creation - STATUS_CREATED
executedBy: ID of the executor
buildNo: Build Number specified in the Test Plan Trigger call
environment: Environment parameter selected for the Test Plan
triggeredType: Triggered type for the Test Plan whether by API or via Testsigma App
totalRunningCount: Total number of running tests
page_timeout: Global Page load timeout in seconds
element_timeout: Global Element load timeout in seconds
recovery_action: Action to be performed on test failure - "Run_Next_Testcase"
on_aborted_action: Action to be performed on test abort - "Reuse_Session"
screenshot_option: When to take screenshots - "FAILED_STEPS", "ALL_STEPS", "NONE"
group_prerequisite_fail: Action to perform on Test Suite prerequisite failure
test_case_prerequisite_fail: Action to perform on Test Case prerequisite failure
test_step_prerequisite_fail: Action to perform on Test Step prerequisite failure
totalQueuedCount: Total number of queued tests