Generating Tests

Create tests using the E2E Builder or code generation.

Paragon generates tests for you. Describe what you want to test, and Paragon writes the code. There are two ways to generate tests depending on the type.

Test Generation Methods

E2E Builder (Step-Based Tests)

The E2E Builder creates browser-based tests that run against your deployed application.

Creating an E2E Test

1. Go to Testing > Tests
2. Click New Test
3. Select the repository for this test
4. Choose E2E as the test type
5. You're redirected to the visual builder

Building Steps

The E2E Builder provides a visual interface to create test flows:

Navigation Steps

Interaction Steps

Agentic Steps

Use natural language for complex interactions:

Agentic steps are powerful for complex flows. Instead of specifying exact selectors, describe what you want in plain English.

Assertion Steps

Data Steps

Authentication in E2E Tests

If your tests need to access protected pages, you can record your login flow directly in the E2E builder.

Setting Up Auth

In the E2E builder:

1. Click the key icon to start recording authentication
2. Log in to your app in the browser
3. Paragon captures your auth session
4. Save your test - the auth is saved with it

Future test runs will use the captured session to authenticate automatically.

Use a dedicated test account when recording authentication.

Running E2E Tests

E2E tests run against your deployed application (production, staging, or preview URL).

E2E tests cannot run on PR events because there's no deployed app yet. They run:

• Manually: Click run button
• On Schedule: Daily, weekly, custom
• On Push: After merge to production (if base URL is production)

E2E Test Results

After running, view:

• Step-by-step breakdown: Each step with pass/fail and duration
• Screenshots: Captured at each step
• Video recording: Full test playback
• Console logs: Browser console output
• Network requests: API calls made during test
• Accessibility violations: WCAG issues detected

Code Test Generation (Unit & Integration)

Generate unit and integration tests that live in your repository.

Creating Code Tests

1. Go to Testing > Tests
2. Click New Test and select the repository
3. Choose Unit or Integration as the test type
4. Switch to the Generate New tab
5. You're redirected to the agent — describe what to test in natural language
6. Review the generated test code
7. Save directly or create a PR with the test

Writing Good Prompts

The better your prompt, the better the generated test.

Unit Test Prompts

Be specific about the function and expected behavior:

Test the calculateDiscount function:
- Returns 0 for orders under $50
- Returns 10% off for orders $50-$100
- Returns 20% off for orders over $100
- Throws error for negative amounts

Integration Test Prompts

Specify the endpoint, inputs, and expected outputs:

Test POST /api/users/register:
- Returns 201 and user object for valid email/password
- Returns 400 for invalid email format
- Returns 409 if email already exists
- Password is not included in response

Supported Frameworks

Paragon generates tests in your preferred framework:

Framework is detected from your project config or can be manually specified.

Code Test Results

After running, view:

• Test output: Standard framework output
• Assertion results: Each assertion with pass/fail
• Coverage (if enabled): Lines covered by test
• Duration: Time to run each test

Performance Tests

Create tests that measure page load performance.

Creating Performance Tests

1. Go to Testing > Tests
2. Click New Test and select the repository
3. Choose Performance as the test type
4. Enter the pages to test
5. Configure performance thresholds (budgets)
6. Set network and CPU throttling conditions
7. Run the test

Performance Budgets

Set thresholds for key metrics:

Test Conditions

Simulate real-world conditions:

Network Throttling:

• 4G (typical mobile)
• Fast 3G
• Slow 3G
• No throttling

CPU Throttling:

• No throttle
• 2x slowdown
• 4x slowdown
• 6x slowdown

Iterations:

• Run 1-10 times for consistent results

Test Organization

Suites

Tests are organized into suites (folders):

Repository: my-app
├── Suite: Authentication
│   ├── Test: Login flow (E2E)
│   ├── Test: Registration (E2E)
│   └── Test: validateEmail (Unit)
├── Suite: API
│   ├── Test: GET /users (Integration)
│   └── Test: POST /orders (Integration)
└── Suite: Performance
    └── Test: Homepage load

When creating a test:

• Add to an existing suite
• Create a new suite

Editing Tests

Click any test to:

• Update name or description
• Regenerate code with new prompt
• Move to different suite
• Delete test

Next Steps