How to Run and Monitor Tests

Learn how to execute tests, monitor their progress, and analyze results with screenshots and detailed logs.

Running a Single Test

Running Multiple Tests

Using Bulk Selection

1. Go to Test Cases
2. Check the boxes next to tests you want to run
3. Click ‘Run Selected’ in the toolbar
4. All selected tests will execute in parallel

Using Test Plans

For regular test runs, create a test plan:

1. Go to Test Plans
2. Create a new plan
3. Add tests to the plan
4. Run the entire plan with one click

Learn more about Test Plans →

Understanding Test Results

Result Status

Result Details

Each execution result includes:

Summary Section:

• Overall status (Pass/Fail)
• Total duration
• Number of steps executed
• Timestamp

Step-by-Step Breakdown:

• Status of each step
• Screenshots (if enabled)
• Error messages (for failures)
• Element selectors used

Execution Logs:

• Detailed console output
• Network requests
• Browser errors
• AI agent decisions

Screenshots

Screenshots are captured:

• After each step (configurable)
• On failures (always)
• On assertions (optional)

Click any screenshot to view full-size with zoom and pan.

Monitoring Real-Time Execution

While tests are running, you can:

Watch Live Progress:

• See which step is currently executing
• View live screenshots as they’re captured
• Monitor execution time

View Browser:

• See the actual browser window (if headless mode is disabled)
• Watch interactions happen in real-time

Cancel Execution:

• Click ‘Cancel’ to stop a running test
• Useful if you notice an issue early

Analyzing Failures

When a test fails, investigate using:

1. Error Message

The error message tells you what went wrong:

Error: Element 'Button with text Sign In' not found

2. Screenshot

The screenshot shows the page state when the failure occurred:

• What was visible on the page?
• Was the element missing?
• Was it hidden or covered?

3. Logs

Console logs provide technical details:

• Network errors
• JavaScript errors
• API call failures
• Timing issues

4. Step Context

Review the failed step configuration:

• Was the selector correct?
• Was the expected value accurate?
• Was there enough wait time?

Re-Running Tests

After fixing issues, re-run tests:

Quick Re-Run:

1. From the results page, click ‘Re-run Test’
2. Latest version of the test will execute

Compare Results:

• Results history shows all executions
• Compare failures across runs
• Identify flaky tests

Scheduling Tests

Run tests automatically:

Via Test Plans:

1. Create a test plan
2. Set a schedule (hourly, daily, weekly)
3. Tests run automatically

Via CI/CD:

• Trigger tests from your deployment pipeline
• Run tests after each deployment
• Block deployments on test failures

Learn more about CI/CD integration →

Execution History

View all past executions:

1. Go to Test Cases
2. Click on any test
3. View the ‘Execution History’ tab

Filter executions by:

• Date range
• Status (passed/failed)
• Duration

Export data:

• Download results as CSV
• Generate PDF reports
• Export via API

Performance Metrics

Track test performance:

Execution Duration:

• Average execution time
• Slowest steps
• Performance trends over time

Pass Rate:

• Historical pass rate
• Failure patterns
• Flaky test detection

View in Analytics →

Best Practices

Next Steps

• Set up notifications to get alerted on failures
• Create test plans for automated test runs
• Use analytics to track pass rates and trends