Skip to main content

Test Runs

A test run is an execution session where you work through a set of test cases and record the results. Test runs are how testing actually gets done in ProvaLab.io.

Create a Test Run​

  1. Click Test Runs in the left sidebar or project navigation.
  2. Click + New Test Run.
  3. Fill in the basic information:
    • Name -- A descriptive name (e.g., "Sprint 15 Regression - Staging" or "Hotfix 3.2.1 Smoke Test").
    • Project -- Select the project (pre-filled if you are already in a project).
    • Environment -- The environment you are testing against (Development, Staging, Production).
  4. Choose how to add test cases (see below).
  5. Click Create Test Run.

Add Test Cases to the Run​

You can add test cases in three ways:

Option A: From a Test Plan Select a test plan and all its test cases are included with their assignments.

Option B: From Test Suites Select one or more test suites. All test cases in those suites are included.

Option C: Manual Selection Click Add Test Cases, search or browse for individual test cases, select them, and click Add Selected.

tip

If you run the same set of tests regularly (e.g., weekly regression), create a test plan or save a test run as a template. This saves you from re-selecting test cases every time.

Assign Testers​

  1. In the Assigned To field, select one or more team members.
  2. Optionally, use Split Work to divide the test cases evenly among the assignees.

Set a Schedule (Optional)​

  • Start Time -- Choose "Immediate" or schedule a future start time.
  • Deadline -- Set an optional completion deadline to track time remaining.

Add Configuration (Optional)​

FieldExample
BrowserChrome, Firefox, Safari, Edge
Operating SystemWindows 11, macOS Sonoma, Ubuntu 22.04
Build Numberv3.2.1-build-456
Custom FieldsAny additional metadata your team tracks

Execute a Test Run​

Start Execution​

  1. Open the test run.
  2. Click Start Execution.
  3. ProvaLab.io displays the first test case with its preconditions, steps, and expected results.

Record Results for Each Test Case​

Follow the test steps on your application under test, then record the outcome:

Pass​

  1. Click Pass (or press P).
  2. Optionally add a comment (e.g., "Verified on Chrome 120").
  3. Click Next Test Case.

Fail​

  1. Click Fail (or press F).
  2. Enter the failure reason (required). Be specific about what went wrong.
  3. Indicate which step failed.
  4. Optionally attach a screenshot, video, or log file.
  5. Optionally click Log Defect to create a bug report linked to this failure.
  6. Click Next Test Case.

Skip​

  1. Click Skip (or press S).
  2. Enter the reason for skipping (e.g., "Feature not yet deployed to staging").
  3. Click Next Test Case.

Blocked​

  1. Click Blocked (or press B).
  2. Explain the blocking issue (e.g., "Database is down, cannot access user data").
  3. Optionally link to the blocking defect or issue.
  4. Click Next Test Case.

Attach Evidence​

For any result, you can attach files as evidence:

  1. Click Attach File or drag and drop files.
  2. Supported file types: images (PNG, JPG), videos (MP4, WebM), log files (TXT, LOG), HAR network captures, and more.
  3. Add a description for the attachment.
tip

Always attach a screenshot when recording a failure. It helps developers understand the issue without needing to reproduce it, and it creates a clear record of what happened.

Track Progress During Execution​

While a test run is in progress, everyone on the team can see:

  • A live progress bar showing how many tests have been executed.
  • Real-time status updates -- no page refresh needed (powered by WebSocket).
  • Who is working on what -- team member avatars appear next to the tests they are currently executing.

Complete a Test Run​

After all test cases have been executed:

  1. Click Complete Run.
  2. Review the summary statistics (pass rate, total duration, breakdown by status).
  3. Add any overall comments about the run.
  4. Click Finish.

The run status changes to Completed and results are locked.

Cancel a Test Run​

If a test run needs to be stopped before completion:

  1. Open the test run.
  2. Click Cancel Run.
  3. Enter a reason for cancellation.
  4. Click Confirm.

Cancelled runs preserve any results that were already recorded. Unexecuted test cases are marked as "Not Run."

Rerun a Test Run​

To repeat a test run (e.g., after bug fixes):

  1. Open a completed or cancelled test run.
  2. Click Rerun.
  3. ProvaLab.io creates a new test run with the same configuration.
  4. Optionally, choose to rerun only failed tests or all tests.
  5. Click Create Rerun.

Test Run Templates​

Save time by creating templates for test runs you execute regularly:

  1. Create a test run with your desired configuration.
  2. Click Save as Template.
  3. Give the template a name (e.g., "Weekly Regression - Staging").
  4. The next time you create a run, click Use Template and select it.

Templates save the test case selection, environment settings, and configuration fields. You still need to assign testers and set the schedule for each new run.