Promoted Tests

Run tests automatically on a schedule or via CI/CD.

Promoted Tests

Promoted tests are tests you've validated and want to run automatically. They form your regression test suite.

What Are Promoted Tests?

When you generate a test with the chat interface:

  1. It runs once to verify it works
  2. If you're happy with it, you can promote it
  3. Promoted tests run automatically based on your configuration

Promoting a Test

  1. Generate and run a test via chat
  2. Review the results to ensure it passes
  3. Click Promote to add it to your test suite
  4. Choose when it should run:
    • On schedule (daily, weekly)
    • On every push (via CI/CD)
    • Both

Scheduling Tests

Promoted tests can run on a schedule:

| Schedule | Description | |----------|-------------| | Daily | Runs every day at a specified time | | Weekly | Runs once a week on a specified day | | On push | Runs when code is pushed (requires CI/CD setup) |

Configure scheduling in Project Settings > Test Schedule.

Managing Promoted Tests

View and manage promoted tests in the Tests tab:

  • View all: See all promoted tests
  • Run now: Trigger a test run manually
  • Edit: Modify the test description or code
  • Unpromote: Remove from automated runs
  • Delete: Remove the test entirely

Test Run History

For each promoted test, you can see:

  • Run history (last 30 days)
  • Pass/fail trends
  • Average duration
  • Failure patterns

Handling Failures

When a promoted test fails:

  1. Notification: You're notified via email or webhook
  2. AI Analysis: AI analyzes the failure
  3. Options:
    • Auto-fix (if AI can fix it)
    • Manual review
    • Temporarily disable

Re-validating Tests

After UI changes, some tests may need updates:

  1. Run the test to see if it still passes
  2. If it fails, use chat to update it:
    • "Update this test - the button text changed to 'Submit Order'"
  3. Re-promote the updated test

Organizing Tests

Use tags to organize promoted tests:

#login #auth          - Authentication tests
#checkout #e2e        - E-commerce flow tests
#regression #critical - Critical regression tests

Filter tests by tag in the Tests tab.

Best Practices

  1. Start small: Promote a few critical tests first
  2. Review regularly: Check test results weekly
  3. Update promptly: Fix broken tests quickly
  4. Tag consistently: Use consistent tag naming
  5. Prioritize critical paths: Focus on user-critical flows

Next Steps