← Back to Docs

Test Execution

Run tests with real-time monitoring

Execute your generated tests in isolated environments with comprehensive monitoring and detailed results.

Running Tests

Start Execution:

Test Plan → Run Test

Execution Process:

  1. Steps execute sequentially
  2. Real-time progress updates
  3. HTTP request/response capture
  4. Variable extraction after each step

Monitor Progress

  • ✅ Completed: Step passed
  • ⏳ Running: Step in progress
  • ❌ Failed: Step encountered error
  • ⏭️ Skipped: Step not executed (after failure)

Understanding Results

Success (✅)

All steps completed successfully:

✅ Step 1: Create user
   Duration: 1.2s
   Status: 201 Created
   Variables: user_id=123

✅ Step 2: Verify user exists
   Duration: 0.8s
   Status: 200 OK

Failure (❌)

Step encountered an error:

❌ Step 2: Verify user exists
   Duration: 0.8s
   Error: AssertionError: Expected status 200, got 404

   Request: GET https://api.example.com/users/123
   Response: 404 Not Found

Execution Details

Console Output

View all print statements and logs from your test code.

HTTP Traffic Capture

Detailed request/response for each API call:

Request:

POST https://api.example.com/users
Headers:
  Content-Type: application/json
  Authorization: Bearer eyJ0eXAi...
Body:
  {"name": "John Doe", "email": "john@example.com"}

Response:

201 Created
Body:
  {"id": 123, "name": "John Doe", "email": "john@example.com"}

Variable State

Track variables throughout execution:

After Step 1:
  user_id = 123
  email = "john@example.com"

After Step 2:
  user_id = 123
  email = "john@example.com"
  access_token = "eyJ0eXAi..."

Error Analysis

Click failed step to see:

  • Error message
  • Stack trace
  • Request/response details
  • Variables at failure

AI Auto-Fix: Click “Analyze Error” for automatic error correction.

Learn more: AI Auto-Fix

Common Failure Reasons

Authentication Issues:

401 Unauthorized → Check credentials

API Not Found:

404 Not Found → Verify base URL and endpoint

Validation Errors:

400 Bad Request → Review request body

Assertion Failures:

AssertionError → Update expected value

Safety Features

Code Validation

Before execution, code is checked for:

  • Syntax errors
  • Undefined variables
  • Variable shadowing

Execution Limits

  • Timeout: 180s default per step
  • Isolation: Sandboxed environment
  • Security: Credentials sanitized in logs

Next Steps

← Back to Documentation