Skip to main content
Version: 1.0.7

Test Sets

Test sets organize repository cases into a hierarchy. A case must have a destination set when it is created manually or saved from an AI Test Session.

Create a test set​

Open Test Repository → Actions → New Test Set. Enter a clear set name and choose its required parent. The parent determines where the set appears in the repository tree.

New test-set draft requiring a parent

If there is no suitable parent, review the existing hierarchy before adding another branch. Avoid creating almost identical roots or feature names.

Design a useful hierarchy​

A practical hierarchy reflects stable ownership and product structure, for example:

Product
├── Authentication
│   ├── Sign in
│   └── Password recovery
└── Checkout
    ├── Payment
    └── Order confirmation

Keep release, sprint, environment, priority, and execution status in labels or workflow metadata when they change frequently. Deeply nesting temporary states makes cases hard to find and reuse.

Choose a destination for generated cases​

After cases pass review in an AI Test Session:

  1. Select the Approved cases.
  2. Choose Save to Repository.
  3. Select the destination test set.
  4. Confirm the save.
  5. Open the repository and verify the cases under that set.

Do not create a new test set for every AI session. Reuse a stable destination when the cases cover the same product area.

Create a case in a set​

Use New Test Case and select the intended set in the Details stage. The chosen set is required before the case can be completed.

Maintain sets​

  • Use concise, distinct names.
  • Review parent placement before creating a set.
  • Keep related cases together without turning one set into an unbounded catch-all.
  • Search before adding a new set to prevent duplicates.
  • Move or rename sets carefully so team members can still locate established coverage.
  • Inspect descendants before deleting a parent.

Set design checklist​

  • Does the set describe a stable feature, component, or testing responsibility?
  • Is there already a suitable set?
  • Is the selected parent correct?
  • Can a teammate predict where a case belongs?
  • Will the structure remain useful beyond the current release?