A Test Log records the result of a test step within a Test Run. Use it to capture what happened, compare the actual outcome with the expected result, and add evidence that helps your team investigate failures.
A Test Run represents one execution of a Test Case. For a multistep Test Case, each step has its own execution log. Plain Text and BDD scripts are recorded at the script level rather than as separate multistep action rows.
What you can record
Information | What to include |
Step result | Select an available result, such as Passed, Failed, or Untested. Result names and availability depend on your workspace and Jira space settings. |
Actual Result | Describe what happened during this execution, especially how it differed from the expected result. |
Execution evidence | Attach relevant screenshots, files, or other evidence to the step’s log. |
Linked work items | Associate relevant Jira work items, such as a bug raised for the failure. |
The step’s action and expected result describe what to test. The actual result and evidence explain what happened when you performed that test.
Record a step result
Open the Test Run you want to update. See Understanding and Viewing Test Runs if you need help finding it.
In Test Execution, review the step’s action and expected result, then perform the action.
Click the step’s result control and select the appropriate outcome.
Enter what happened in Actual Result. Save your changes if the editor shows a Save button.
Under Execution Evidence, select Add to attach supporting files when needed.
Repeat for the remaining steps, then review the run’s overall result and completion progress.
You need access to the Jira space and permission to execute Test Cases to record or change results.
Example: investigate a failed login
Sarah executes a Login Test Case in UAT. She completes all three steps and records the following results:
Step | Expected result | Actual result | Result |
1. Open the login page | The login form appears. | The login form appeared. | Passed |
2. Enter valid credentials | The fields accept the credentials. | Both fields accepted the values. | Passed |
3. Select Sign In | The dashboard opens. | An error message appeared; the dashboard did not open. | Failed |
This creates one Test Run with three step logs. The completed run’s overall result is Failed. Sarah can attach a screenshot of the error and link the relevant bug to support the failed step.
If steps are still Untested or in progress, the overall result can also show an in-progress state. Review the individual logs and remaining steps before treating the run as complete.
Keep execution records clear
Record the observed outcome rather than copying the expected result.
Add enough detail to reproduce a failure, such as the error message and relevant test data.
Update the existing run when continuing the same execution. Create a new run when performing a separate retest so both executions remain available.
Use the run’s timer or work log for execution time. See Time Tracking for Test Execution.
Send step results from automation
Use the Test Step Result API to record outcomes and actual results from your integration. To add screenshots or reports, see Attach Files to a Test Step.