Skip to main content

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

Overview of Scenario Tables

Understanding the structure:
  • 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. Scenario Tables section with New Scenario and Import via CSV buttons
Best for small datasets
1

Click New Scenario Table

Click New Scenario Table.
2

Enter table details

  • Scenario Table Name: Choose a descriptive name
  • Description: Explain what scenarios this table covers New scenario table form with name and description fields
3

Create your table

Click Create Scenario Table.
4

Add your data

Click Add scenario to add a row, or press Cmd+Enter (Mac) or Ctrl+Enter (Windows). Click + (Add column) beside the column headers to add a column.
5

Save your changes

Click Save edits, or press Cmd+S (Mac) or Ctrl+S (Windows).
Scenario table editor with rows and property columns

Step 2: Connect your table to a test

Scenario Tables must be connected to Test Suites, not individual tests. Once connected to a suite, all tests within that suite can use the scenario properties.

How it works

  1. Connect the Scenario Table to a Test Suite
  2. Use the properties [property_name] in any test within that suite
  3. Run the suite to execute all scenarios across all tests
Now you’ll connect your Scenario Table to a test suite. You can do this in two ways:

Option 1: Through the Test Suites menu

1

Go to Test Suites

Navigate to the Test Suites section
2

Select your Test Suite

Choose the test suite you want to connect to a scenario table
3

Access suite menu

Click the three-dot menu (⋯) next to your test suite
4

Connect Scenario Table

Select “Connect Scenario Table” from the dropdown menu
5

Choose your table

Select the scenario table you want to connect to this test suite

Option 2: Through the test editor

1

Create or edit a test

Open the test editor for your chosen test
2

Add scenario variables

In the test editor:
  • 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]”)
Property names will auto-complete as you type, making it easy to reference your scenario data.

Step 3: Run and monitor your tests

After saving your scenario-based test:
1

Execute your test

Click “Run” to execute all scenarios
2

View results

Check results in Run History, broken down by scenario:Run History results broken down by scenario
  • Example: Separate results for DFW scenario and LAX scenario
3

Inspect individual scenarios

Click each scenario to inspect individual steps and outcomes Clicking a scenario to inspect its steps and outcomes
4

Schedule recurring runs

Schedule recurring runs just like a regular test suite Scheduling recurring runs for a scenario suite

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.
This is especially useful for large scenario tables where you need to quickly find a scenario by one of its data values. For example, search by city name, email, or any other property.

Managing scenarios

Use the switch in the Status column to make a scenario active or inactive without deleting it. Inactive scenarios are dimmed. They are skipped when connected suites run, but you can still pick them by hand for a run. To change several at once, select the rows and click Mark as active or Mark as inactive.
Click any cell in the scenario table to edit its value. Edits are not saved until you click Save edits or press Cmd+S (Mac) or Ctrl+S (Windows). The toolbar shows how many unsaved changes you have.
Click Add scenario at the bottom of the table, or press Cmd+Enter (Mac) or Ctrl+Enter (Windows). When the table reaches 1,000 scenarios, the button shows Limit reached.
Select scenarios and click Delete scenario (or Delete scenarios) in the selection bar. Spur marks them for deletion and removes them when you save.
Open the table’s More actions menu (⋯) and select Import CSV. Choose Add to table to append the rows, or Replace table to overwrite the table’s data.
Drag a property column header to move it. The fixed Scenario Name and Status columns stay in place.
Click the filter icon in the toolbar and select Active or Inactive to show only scenarios with that status.
Open the table’s More actions menu (⋯) and turn on Full width. Spur remembers this setting for each table in your browser.

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. Click Show affected rows to see which rows are duplicates and what they match.

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

Key benefits

Reduce redundancy

Write one test instead of many duplicate tests. A single parameterized test can handle dozens of scenarios without duplicating test logic.

Easier maintenance

Update inputs in one central location. When test data needs to change, modify the scenario table rather than updating multiple individual tests.

Better test coverage

Easily test variations and edge cases. Add new scenarios to your table without modifying test logic, enabling comprehensive coverage of input combinations.

Scalability

Add new scenarios as table rows — no new test steps required.