What are scenario tables?
Scenario Tables let you run one test across many data variations. Instead of creating multiple nearly identical tests with different inputs, you can write one test that dynamically runs through multiple scenarios defined in a table.
Overview of Scenario Tables
- Each row = one scenario (test variation)
- Each column = one property (variable you’ll use in tests)
- A table can hold up to 1,000 scenarios
How to set up scenario tables
Step 1: Create your scenario table
Navigate to the Scenario Tables section in Spur. Click New Scenario Table to start with an empty table, or Create using CSV to build it from a file.
- Manual creation
- Import via CSV
Click New Scenario Table
Enter table details
- Scenario Table Name: Choose a descriptive name
-
Description: Explain what scenarios this table covers

Create your table
Add your data
Cmd+Enter (Mac) or Ctrl+Enter (Windows). Click + (Add column) beside the column headers to add a column.Save your changes
Cmd+S (Mac) or Ctrl+S (Windows).
Step 2: Connect your table to a test
How it works
- Connect the Scenario Table to a Test Suite
- Use the properties
[property_name]in any test within that suite - Run the suite to execute all scenarios across all tests
Option 1: Through the Test Suites menu
Go to Test Suites
Select your Test Suite
Access suite menu
Connect Scenario Table
Choose your table
Option 2: Through the test editor
Create or edit a test
Add scenario variables
- Type
[to open the scenario variable menu - Select your Scenario Table (e.g., “Flight List Table”)
- Insert properties into test steps (e.g., “Type [From_city]”)
Step 3: Run and monitor your tests
After saving your scenario-based test:Execute your test
View results

- Example: Separate results for DFW scenario and LAX scenario
Inspect individual scenarios

Schedule recurring runs

Searching scenarios
When selecting scenarios to run, you can search across all property values, not just the scenario name. Type any value that appears in your table and matching scenarios will be filtered and highlighted instantly.Managing scenarios
Activate or deactivate scenarios
Activate or deactivate scenarios
Edit scenarios
Edit scenarios
Cmd+S (Mac) or Ctrl+S (Windows). The toolbar shows how many unsaved changes you have.Add new scenarios
Add new scenarios
Cmd+Enter (Mac) or Ctrl+Enter (Windows). When the table reaches 1,000 scenarios, the button shows Limit reached.Delete scenarios
Delete scenarios
Import a CSV into an existing table
Import a CSV into an existing table
Reorder columns
Reorder columns
Filter scenarios
Filter scenarios
Use the full width of the page
Use the full width of the page
Leaving with unsaved edits
If you try to leave a table with unsaved edits, Spur asks you to confirm. Click Keep editing to stay on the page, or Leave without saving to discard your edits.Review duplicate scenarios
When you import a CSV, Spur checks for rows that share a scenario name with another row. It compares rows within the file. With Add to table, it also compares them against rows already in the table. Spur sorts duplicates into two groups, and you choose what to do with each group before importing.Best practices
- Start simple: Begin with 2-3 scenarios to validate your test logic before scaling up
- Use descriptive scenario names: Make it easy to identify which scenario failed in test results
- Organize related scenarios together: Group similar test variations in the same scenario table
- Keep variables consistent: Use the same variable names across related tests for easier management
- Test with one scenario first: Verify your test works correctly with a single scenario before adding more
- Document edge cases: Use scenario names to clearly indicate boundary conditions or special cases



