4.5 Adding Test Cases to Multiple Suites (Zero Duplication)

How a single test case can be assigned to multiple test suites (Smoke, Nightly, Critical Path) with automatic synchronization.

One Case, Several Pipelines

A checkout case often needs to run in more than one place at once: Smoke on every pull request for fast feedback, Nightly for broader unattended coverage, and Critical Path as a release gate before anything ships. Without a way to put one case in several suites, a team either clones the case three times – and the clones start drifting within a month, the same maintenance problem CertiBlocks solve for shared steps (see 4.1), just at the case level instead – or forces one suite to serve three different schedules and gates it was never meant to.

The Parent Suites multi-select on a case’s settings tab solves it directly: check every suite this case belongs to, and CertiQA treats it as one definition referenced from each of them, not a copy per suite. Edit a step or an assertion once, and every suite that includes the case reflects the change on its very next run – a tester reviewing the Nightly results and one reviewing Smoke are looking at the literal same case, not near-duplicates that can quietly diverge.

Membership Isn’t Schedule

• A case’s suite memberships say which suites run it, not how or when – Smoke can run that same case against staging on every push while Critical Path runs it against a production-mirrored environment right before release. What varies per suite is the suite’s own schedule and target environment, not the case definition itself.