Skip to content
OttoTester docs

Test suites

What a test suite is

Section titled “What a test suite is”

A test suite is a named group of tests, scoped to a variant. It’s a convenience: instead of running every test, or hand-picking tests each time, you save the set once and run it as a unit.

Common suites:

  • A smoke suite — a handful of critical-path tests, fast to run.
  • A regression suite — the full set, run before a release.
  • A feature suite — everything touching one area, like checkout or sign-up.

A test can belong to more than one suite — your smoke suite and your regression suite can share tests.

What you do with a suite

Section titled “What you do with a suite”

A suite is the natural unit for running tests:

Because a suite can be a CI/CD entry point, deleting one that a pipeline depends on is a real hazard. OttoTester guards against it: a suite marked as a CI entry point needs an explicit confirmation to delete, and deleted suites stay recoverable for 30 days.

Create a suite

Section titled “Create a suite”

In a variant, open the Suites page and click New suite. Give it a name, then pick the tests that belong — filter by intent, priority, or recent status to build up the set quickly.

A test can be in more than one suite, so you don’t need to “move” tests between suites — just add the same test to each suite it belongs in (a smoke set and a regression set can both include the same login test, for example).

Once you have the suite, run it on demand with a replay template, point a schedule at it, or wire it into CI/CD.

Section titled “Related”