Skip to main content

Test Case Execution View

When you select a specific test case from the list within an active Test Run, the right panel changes to show the details for executing that case within the context of the run.

This view allows you to follow the test steps, record results, add comments, and manage attachments specific to this execution.

Layout and Components​

This view typically includes:

  1. Header:

    • Test Case Name: Displays the name of the test case being executed.
    • Current Status: Shows the current overall status (e.g., Untested, Passed, Failed, Blocked) for this case within this specific run.
    • Navigation: May include Previous/Next buttons to move between test cases in the run sequence without returning to the main list.
    • Close Button (X icon): Returns the right panel to the default Test Run metadata view.

  2. Overall Result Controls: Buttons to set the overall status for the entire test case within this run:

    • Pass (Check icon): Marks the entire case as passed.
    • Fail (X icon): Marks the entire case as failed.
    • Block (CircleSlash icon): Marks the case as blocked (e.g., due to an environment issue or dependency).
    • Skip (SkipForward icon): Marks the case as skipped.
    • (Setting an overall result might automatically update step results accordingly, depending on configuration.)

  3. Steps List: Displays the steps defined in the test case, usually including:

    • Step Number/Order.
    • Action/Description: The instruction for the step.
    • Expected Result: What should happen after performing the action.
    • Step Result Controls: Individual Pass/Fail/Block/Skip buttons for each step. Setting a step result often updates the overall case result automatically (e.g., failing one step fails the case).
    • Step Comment Area: An optional field to add notes specific to the execution of that step.
    • Step Attachments: An option to attach files (screenshots, logs) directly related to the result of that specific step.

  4. Overall Comments: A rich-text editor area to add comments relevant to the overall execution of the test case in this run (e.g., explaining why it was blocked, general observations).

  5. Overall Attachments: An area to upload and view attachments relevant to the overall execution result of this test case within the run.

Execution Workflow​

  1. Select Case: Click a test case from the list in the left panel of the Test Run Details page.
  2. Review Steps: Read the action and expected result for each step.
  3. Perform Action: Execute the test step action in the system under test.
  4. Record Step Result: Click the Pass, Fail, Block, or Skip button for the step based on the outcome.
  5. Add Step Details (Optional): Add comments or attach files directly to the step if needed.
  6. Repeat: Continue for all steps.
  7. Set Overall Result: If not automatically set by step failures, use the overall result buttons at the top.
  8. Add Overall Details (Optional): Add overall comments or attachments.
  9. Navigate/Close: Use the Previous/Next buttons or Close button to move to another case or return to the run overview.

Result Validation and Editing​

A project can apply rules that govern how results are recorded and corrected. These are configured by administrators and surface during execution:

  • Required result fields: If the case's template includes a required Result Field, the result can't be saved without it. The quick Pass & Next button (and per-iteration quick-status buttons) open the full Add Result dialog, pre-set to the chosen status, so you can fill in the required field before saving.
  • Result edit window: After a result is recorded, it can be edited in place only for as long as the project's Result Edit Window allows. Once that window closes, recording a correction creates a new attempt instead of overwriting the existing result, so the full history is preserved. System administrators can always edit a result.
  • Flip justification: If the project requires justification on a result flip, changing one completed outcome to a different completed outcome prompts for Result Details explaining the change before the result is saved. This covers any pair of completed statuses whose pass/fail judgment differs — including changes to or from any status marked as Completed on the Admin > Statuses page. Moving to or from a non-completed status (Untested, Retest, Blocked) is not gated.
  • Issue on failure: If the project requires a linked issue on failure, recording a failure status (any status marked Failure on the Admin > Statuses page) requires at least one linked issue — on the result or on a failing step. Choosing a failure status from a quick-status button opens the Add Result dialog with a prompt to link an issue before saving.