Test case formats

Each test case has a Type: Manual (steps), BDD (Gherkin) or Generic (narrative). You can switch type at any time; the content is converted for you.

Manual steps

Manual test cases have a step table with three columns: Action, Data and Expected result.

• Click Add step to add a row, drag rows to reorder them, and use Delete step to remove one.
• Steps are plain text. Attach screenshots and other evidence to the run when you execute the case.

Shared steps (call another test case)

Use Insert call to test case to reuse the steps of another case, such as a common login flow. Search by name or TC number. When the test runs, the called case’s steps appear in place of the call, marked Shared step from TC-n. Changes to the called case apply everywhere it is called.

If the called case is later deleted, the step shows as unavailable so you can replace it.

Datasets (data-driven testing)

Open Dataset to run the same steps against several sets of data.

1. Add columns, for example email and password, and one row per data set.
2. Use the column names as placeholders in your steps: <email> or {{email}}.
3. When the case runs, it runs once per row with the placeholders replaced by that row’s values.

A dataset holds up to 30 columns and 200 rows. The editor warns you about placeholders that do not match a column.

Suggest rows with AI proposes extra rows from your steps, with optional guidance such as EU phone numbers or boundary values. Each suggestion shows what kind of case it covers. Pick the ones you want and click Add rows, or Discard.

During execution each row becomes a data iteration with its own step results.

BDD (Gherkin)

BDD test cases hold one Gherkin Scenario or Scenario Outline, under a Feature with an optional Background. The editor gives you:

• syntax highlighting and live validation (✓ Valid Gherkin, or the error and its line);
• step autocomplete from steps already used in the project (Ctrl+Space);
• one-key formatting (Alt+L) and comment toggling;
• Gherkin keywords in other languages.

Rename a step everywhere

Rename step… finds a step and rewrites it in every BDD test case that uses it, keeping each step’s own values. Cases that already have execution runs get a new version, so their results stay attached to the wording they were run with.

Feature files

BDD cases map to .feature files: you can import feature files (each scenario becomes a test case), export a folder as feature files, and open Feature view to read a whole folder as features. Automated Cucumber results imported from CI match BDD cases by scenario and feature name.

Generic (narrative)

Generic test cases hold free-form text: a charter, test notes or exploratory intent. Use them for checks that don’t fit a step table. For timeboxed, note-taking exploratory work, use exploratory sessions instead.

Switching type

Changing Type asks you to confirm the conversion, then maps the content: manual steps become Given/When/Then steps, Gherkin steps become action rows, and so on. If the case has execution runs, the converted content is saved as a new version.