Test Run Execution

Learn how to create and execute test runs with real-time tracking and reporting

Creating a Test Run

Step 1: Start New Test Run

Navigate to Test Runs and click "+ New Test Run". Provide:

  • Name: e.g., "Release 2.5 Regression"
  • Description: Purpose and scope of the test run
  • App Version: Version being tested

Step 2: Select Test Cases

Choose test cases to include in this run. You can:

  • Select individual test cases
  • Include entire folders
  • Filter by priority or category
  • Use saved test suites

Step 3: Assign Testers

Assign test cases to team members. You can assign entire categories to individuals or distribute test cases evenly across your QA team.

Executing Tests

Test Execution Interface

Click on a test run to open the execution interface. For each test case:

  • View the test case details and steps
  • Mark status: Pass, Fail, Blocked, or Skip
  • Add execution notes
  • Upload screenshots or attachments
  • Create tickets for failed tests

Status Options

  • Pass: Test executed successfully, all expectations met
  • Fail: Test failed, bug found
  • Blocked: Cannot execute due to external issue
  • Skip: Test skipped (e.g., out of scope for this run)

Multi-Assignee Support

Collaborate effectively with your QA team:

  • Assign different test cases to different testers
  • See real-time progress as team members update statuses
  • Track who executed each test and when
  • Reassign tests if needed during execution

Progress Tracking & Reports

Live Dashboard

View real-time statistics:

  • Overall completion percentage
  • Pass/Fail/Blocked/Skip counts
  • Test cases by assignee
  • Status history timeline

Final Report

Once testing is complete, generate a comprehensive report including:

  • Executive summary
  • Detailed test results
  • All attachments and notes
  • Linked tickets for failed tests
  • Export to PDF for stakeholders

Best Practices

  • Start test runs early in the development cycle
  • Always add notes for failed tests explaining what went wrong
  • Attach screenshots or logs to help developers reproduce issues
  • Create tickets immediately for failed tests to track fixes
  • Review test run results with the team regularly
  • Archive completed test runs for future reference