- Get started
- About
- Glossary
- Create a company-managed project
- Jira permissions
- First steps
- Configuration
- Migration to Cloud
- Use cases
- User's guide
- Project view
- Navigation
- Relations
- Requirement
- Test Case
- Test Plan
- Test Execution
- Defect
- REST API
- REST API
- Authentication
- Test Key
- Jira REST API
- Requirements
- Test Case
- Test Plan
- Test Execution
- Test Case Execution
- Defects
- Tree Structure
- Example of use
Last updated Nov 9, 2020
Test Case Execution
Test Case Execution is a status and description of a particular Test Case’s progress. At this stage, the team members can test, add comments, attachment, and change the results of each Test Case. Test Case Executions are created as testing objects inside the Test Execution step.
Info
To keep our REST API simple and semantically correct, we plan to add small changes in removing defects, both from Test Case Executions and Test Case Execution Steps. Since 29th February 2022, Defect Test Key should be provided in path - not in request body.
Following endpoints will be affected by our changes:
DELETE /api/test-case-execution/{testKey}/defect →
DELETE /api/test-case-execution/{testKey}/defect/{defectTestKey}
DELETE /api/v2/test-case-execution/{testKey}/defect →
DELETE /api/v2/test-case-execution/{testKey}/defect/{defectTestKey}
DELETE /api/v2/test-case-execution/{testKey}/step/{stepId}/defect →
DELETE /api/v2/test-case-execution/{testKey}/step/{stepId}/defect/{defectTestKey}
As you may notice, since 29th February 2022 all endpoints will require {defectTestKey} in the path. It will not require any request body.
V1 API
Note
We recommend you to use V2 instead of V1 API. We’re going to stop supporting V1 in the future.
