Test Collections
Reusable, named sets of test cases - build a smoke pack, a regression pack or a release-candidate pack once, and drop it into as many Manual Test Executions as you need.
Overview
A Test Collection is a curated, named group of test cases assembled across folders and suites, independent of where those cases actually live in the case repository. Build it once - a smoke pack, a regression pack, a payments pack - and reuse it every time you plan a run instead of re-selecting the same cases by hand.
Give a collection a name once, then reference it in every execution that needs the same coverage.
Pull cases from any folder or suite in the repository into a single collection.
Adding a case to a collection does not move it. The case keeps its original folder and suite, and can belong to any number of collections at once.
An AI assistant can build and populate collections over MCP under your own roles and audit log.
Building a Collection
Create a collection, give it a name, and add cases to it from anywhere in the project's folder and suite tree. There is no limit on how many collections a single case belongs to, so the same login test case can sit in a smoke collection and a regression collection at the same time.
Using Collections in a Manual Test Execution
When you build a Manual Test Execution, a collection is one of three sources you can pull from, alongside whole suites and hand-picked individual cases. Add a collection to an execution and every case in it is snapshotted into the run in one step, ready to be assigned and worked through.
- Manual Test Executions covers how executions are assigned, tracked and linked to releases.
Managed by AI over MCP
The same operations are available to an AI assistant through the MCP server: create_test_collection builds the collection, add_cases_to_collection populates it, and add_collections_to_execution drops it into a run. Agent-built collections land in the same repository as everything a person creates by hand.
Coming From Another Tool?
If you know TestRail or Zephyr, a Test Collection is what those tools call a Suite or a Cycle: a reusable, named set of cases you run again and again, kept separate from the folder tree that organizes the case repository itself.