The rail
The Scenarios tab lists the test suites of the project under Test Suites in the rail on the left. Press one to open its scenarios in the table. New Test Suite asks for a name only.
Every project has a Default test suite. A scenario saved with No test suite goes there.
Run a test suite
Run suite, in the rail menu or at the top of the table, opens the run dialog. The run goes under the run plan named after the test suite and the agent, for exampleRefunds checkout-prod, so every run of the same test suite against the same agent joins one history on the Results tab.
Move scenarios between test suites
Move to suite… in the row menu of a scenario opens Move to test suite, which lists the test suites of the project. Select several rows and press Move to suite in the bar that appears to move them together. A scenario belongs to exactly one test suite.
Test suites and labels
A test suite is the group you run before a release. A label is a tag on a scenario, and a scenario can have any number of them. A run plan can scope by labels across every test suite, for example every scenario labelledsmoke, so use labels for a cut that crosses the test suites and a test suite for the group that ships together.
From Code
Scenarios written with the Scenario SDK and run from your own test runner report to the project and appear under From Code in the rail, one entry persetId. Their table is read-only and shows each scenario with its last run. Edit them in your repository. The platform lists them so their results appear next to the test suites written here.
