Test execution

Track every test run against its build

Each run is linked to an app version and an environment snapshot, so results always point back to exactly what was tested.

Run outcomes

Pass, fail, block, and skip, per suite

Execution status

Status summaries by suite

Each suite shows its pass, fail, block, and skip counts for the selected run, making it clear where attention is needed.

Error traces

Trace records for each failure

Failed steps keep their error trace attached to the run, so a failure can be read in the context of the build and environment it came from.

Execution protocol

From suite assignment to consolidated logs

01

Assign the suite

Choose the test suite and the app version to run against, pinned to a specific build.

02

Select the environment

Attach the environment snapshot so the run records the exact server and endpoint configuration.

03

Execute and record

Run tests manually or through automation, recording each outcome as pass, fail, block, or skip.

04

Consolidate the logs

Review the chronological run log to confirm stability across revisions before moving on.