Scenarios (Table-Driven Tests)

​

Overview

• Testing login with multiple user accounts
• Validating form submissions with various input combinations
• Checking search functionality with different queries
• Testing payment flows with different amounts or methods
• Any test that follows the same steps but uses different data

​

Enabling Scenarios

1. Open a test case in the editor
2. Click the Settings icon in the top-right corner
3. Toggle on Table-Driven Tests
4. Click the Scenarios tab to define your data

​

The Scenarios Tab

​

Adding Columns

1. Enter a column name (this becomes the variable name)
2. The column is added to the table
3. Fill in values for each scenario row

​

Adding Rows

1. Enter a descriptive name in the Name column
2. Ensure the Enabled toggle is on
3. Fill in values for each variable column

​

Example Table

​

Using Scenario Variables

{{ scenarios.username }}
{{ scenarios.password }}

​

Example: Login Test with Scenarios

URL: {{ env.BASE_URL }}/login

Selector: [data-test="username"]
Value: {{ scenarios.username }}

Selector: [data-test="password"]
Value: {{ scenarios.password }}

Selector: [data-test="login-button"]

​

Running Tests with Scenarios

1. The test executes once for each enabled scenario
2. Each scenario runs independently with its own data
3. Results show each scenario separately with individual pass/fail status

​

Understanding Results

• Scenario Name: The name you defined in the table
• Status: Pass or Fail for that specific scenario
• Started: When the scenario began execution
• Duration: How long the scenario took

​

Import and Export CSV

​

Export CSV

1. Click Export CSV in the Scenarios tab
2. Save the file to your computer
3. Use for backup, sharing, or editing in spreadsheet software

​

Import CSV

1. Click Import CSV in the Scenarios tab
2. Select a CSV file with matching column structure
3. Scenarios are populated from the CSV data

• First row must be column headers
• Must include name and enabled columns
• Additional columns become variable columns
• enabled values: true/false or 1/0

name,enabled,username,password
correct user,true,standard_user,secret_sauce
normal,true,normal_user,test123
admin login,true,admin,admin_pass

​

Best Practices

​

Naming Scenarios

• Use descriptive names that explain what the scenario tests
• Good: “valid credentials”, “expired password”, “locked account”
• Avoid: “test1”, “scenario2”, “row3”

​

Organizing Variables

• Keep column names short but meaningful
• Use consistent naming: user_email not userEmail in one and user-email in another
• Group related variables logically in the table

​

Managing Large Tables

• Disable scenarios temporarily instead of deleting them
• Use CSV export to version control your test data
• Split very large tables into multiple test cases if needed

​

Debugging Scenarios

• Run individual scenarios by disabling others
• Check variable names match exactly between table and expressions
• Verify all required columns have values for each row

​

Combining with Other Features

​

Scenarios + Environments

URL: {{ env.BASE_URL }}/login
Username: {{ scenarios.username }}

​

Scenarios + Loops

​

Scenarios + Conditionals

Condition: {{ scenarios.user_type == 'admin' }}
  -> Verify admin dashboard visible
Otherwise:
  -> Verify user dashboard visible

​

Troubleshooting

​

Variable Not Found

• Verify the column name in the Scenarios tab matches your expression
• Check for typos and case sensitivity
• Ensure the column exists and has a value

​

Scenario Not Running

• Check that the scenario’s Enabled toggle is on
• Verify Table-Driven Tests is enabled in settings
• Ensure there’s at least one enabled scenario

​

Wrong Values Used

• Confirm you’re using scenarios. prefix, not vars. or env.
• Check the scenario row that ran matches expected values
• Review CSV import if data was imported

​

All Scenarios Fail

• Test with a single scenario first to isolate issues
• Check that step selectors work with the provided data
• Verify environment variables are set correctly