Skip to main content

​
What are Scenario Tables?

Scenario Tables are a powerful feature in Spur that help you simplify and scale your test suites by using parameterized test data. 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.
Screenshot 2026 02 05 At 2 58 27 PM
Understanding the structure:
  • Each row = one scenario (test variation)
  • Each column = one property (variable you’ll use in tests)

​
How to Set Up Scenario Tables

​
Step 1: Create Your Scenario Table

Navigate to the Scenario Tables section in Spur and choose your preferred method: Screenshot 2025-04-28 at 5.39.54 PM.png
Best for small datasets
1

Click 'New Scenario'

Click the New Scenario button
2

Enter table details

  • Scenario Table Name: Choose a descriptive name
  • Description: Explain what scenarios this table covers Screenshot 2025-04-28 at 5.51.43 PM.png
3

Create your scenario

Click “Create Scenario”
4

Add your data

Add your data manually in the table editor
5

Save your changes

Click “Save Edits” when finished
Screenshot 2025-04-28 at 5.11.43 PM.png

​
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 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 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.

Learn More

Detailed guide for using Scenarios in Tests →

​
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:Screenshot 2025-04-28 at 6.05.04 PM.png
  • Example: Separate results for DFZ scenario and LAX scenario
3

Inspect individual scenarios

Click each scenario to inspect individual steps and outcomes clickonscenario.gif
4

Schedule recurring runs

Schedule recurring runs just like regular test suite Screenshot 2025-07-14 at 5.58.05 PM.png

​
Managing Scenarios

Use the toggle switch in the Status column to enable or disable specific scenarios without deleting them. Disabled scenarios won’t run when you execute the test.
Click any cell in the scenario table to edit values directly. Changes save automatically.
Click + New Scenario at the bottom of the table or press the keyboard shortcut to add additional scenario rows.
Select scenarios and use the delete option to remove them from your table.

​
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

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