Zephyr: Create Test Execution
zephyr_create_test_executionCreate a test execution record for a test case in a specific test cycle, setting its status and optional attributes such as environment, execution time, and custom fields.
Instructions
Create a new Test Execution for a Test Case within a specific Test Cycle
Toolset: Test Executions
Parameters:
projectKey (string) required: Jira project key.
testCaseKey (string) required: Key of test case the execution applies to. NOTE: Test cases with call to test, parameters and test data are not supported.
testCycleKey (string) required: Key of test cycle the execution applies to.
statusName (string) required: The status name.
testScriptResults (array)
environmentName (string): Environment assigned to the test case.
actualEndDate (string): The actual end date of the test cycle. Format: yyyy-MM-dd'T'HH:mm:ss'Z'
executionTime (number): Actual test execution time in milliseconds.
executedById (string): Atlassian Account ID of the Jira user.
assignedToId (string): Atlassian Account ID of the Jira user.
comment (string): Comment added against overall test case execution.
customFields (record<string, any>): Multi-line text fields support HTML and should denote new lines with the <br> tag. Dates should be in the format 'yyyy-MM-dd'. Users should have values of Jira User Account IDs.
Examples:
Create a Passed execution for test case SA-T1 in cycle SA-R1
{
"projectKey": "SA",
"testCaseKey": "SA-T1",
"testCycleKey": "SA-R1",
"statusName": "Pass"
}Expected Output: The newly created Test Execution with execution details
Create a Failed execution with execution time, environment and comment
{
"projectKey": "MM2",
"testCaseKey": "MM2-T15",
"testCycleKey": "MM2-R3",
"statusName": "Fail",
"environmentName": "Staging",
"executionTime": 125000,
"comment": "Step 3 failed due to timeout<br>Logs attached."
}Expected Output: The newly created Test Execution including environment and timing information
Create execution with custom fields and assignment
{
"projectKey": "SA",
"testCaseKey": "SA-T5",
"testCycleKey": "SA-R2",
"statusName": "Pass",
"executedById": "5b10ac8d82e05b22cc7d4ef5",
"assignedToId": "5b10ac8d82e05b22cc7d4ef6",
"actualEndDate": "2026-02-17T10:15:30Z",
"customFields": {
"Execution Build": "1.0.3",
"Tested Browser": "Chrome",
"Execution Date": "2026-02-17"
}
}Expected Output: The newly created Test Execution including custom field values
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| comment | No | Comment added against overall test case execution. | |
| projectKey | Yes | Jira project key. | |
| statusName | Yes | The status name. | |
| testCaseKey | Yes | Key of test case the execution applies to. NOTE: Test cases with call to test, parameters and test data are not supported. | |
| assignedToId | No | Atlassian Account ID of the Jira user. | |
| customFields | No | Multi-line text fields support HTML and should denote new lines with the \<br\> tag. Dates should be in the format 'yyyy-MM-dd'. Users should have values of Jira User Account IDs. | |
| executedById | No | Atlassian Account ID of the Jira user. | |
| testCycleKey | Yes | Key of test cycle the execution applies to. | |
| actualEndDate | No | The actual end date of the test cycle. Format: yyyy-MM-dd'T'HH:mm:ss'Z' | |
| executionTime | No | Actual test execution time in milliseconds. | |
| environmentName | No | Environment assigned to the test case. | |
| testScriptResults | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | The ID of the entity | |
| self | No |