Test Suites

Test suites organize your test cases into logical groups. They also control execution order and can override project settings.

Creating a Test Suite

1. Open your project
2. Click the + icon next to "Test Suites" in the sidebar
3. Enter a suite name
4. Click Create

Suite Types

Regular Suites

Standard test suites that group related tests. Examples:

• "User Authentication"
• "Shopping Cart"
• "Checkout Flow"
• "User Profile"

Login Suites

Special suites that handle authentication:

1. Create a suite with login test(s)
2. Enable Login Suite in suite settings
3. After successful execution:
   • Cookies and session are saved
   • Storage state is applied to subsequent suites

Cleanup Suites

Suites that run after all other tests:

1. Create a suite with cleanup tests
2. Enable Cleanup Suite in suite settings
3. Use for:
   • Deleting test data
   • Resetting application state
   • Logging out

Cleanup suites execute last, even if tests in other suites fail.

Suite Settings

Each suite can override project-level settings:

When to Override

Override settings when:

• Testing different environments (staging vs production)
• Using different user accounts per feature
• Testing with specific authentication states

Execution Order

When running all tests in a project:

1. Login Suites (if any)     → Saves storage state
2. Regular Suites            → Uses saved storage state
3. Cleanup Suites (if any)   → Final cleanup

Within a suite, tests run in the order they appear in the sidebar.

Reordering Tests

Drag and drop tests in the sidebar to reorder them within a suite.

Best Practices

• Group by feature - "Cart", "Checkout", "Profile" instead of "Test 1", "Test 2"
• Keep suites focused - 5-10 tests per suite is manageable
• Use login suites - Don't repeat login steps in every test
• Use cleanup suites sparingly - Only when you need to reset state
• Name descriptively - "User Registration" not "Suite 1"