Managing test cases
Test cases can come from two places, and both appear in Test Executor side by side.
| Source | Where it lives | How you get them |
|---|---|---|
| Core product | Generated from requirements and user stories in the wider platform | Browse Project Tree |
| Test Executor repository | Test Executor's own store | Test Cases page — author or import |
The two are independent. Adding test cases to the Test Executor repository changes nothing about the ones generated in the core product, and you can run both in the same execution.
Authoring a test case
- Go to Test Cases and pick a project, or create one with + New project.
- Pick a folder, or create one. Folders group related tests — Account Creation, Checkout, Smoke.
- Click + New test case.
- Give it a name. Leave the ID blank and it is numbered for you (TC-001, TC-002…).
- Add your steps. Each step has an action and an optional expected result. Use the arrows to reorder.
- Fill in the overall expected result — this one is required.
- Create test case.
Importing from a spreadsheet
If you already keep manual test cases in Excel, import them rather than retyping. Select a folder and use Import test cases from a spreadsheet.
The layout is one row per step, grouped by Test Case ID:
| Test Case ID | Name | Priority | Step # | Action | Expected Result | Overall Expected Result |
|---|---|---|---|---|---|---|
| TC-101 | Browse the collection | P1 | 1 | Click 'Shop the Collection' | The shop page opens | The shop page is displayed with products visible |
| TC-101 | 2 | Verify the 'Roaster's Choice Box' card is shown | The card is visible |
Name, Priority, Overall Expected Result and Preconditions are read from the first row of each group — leave them blank on subsequent rows. Use Download template for a working example.
Column names are matched leniently: case, spacing and common synonyms (TC ID, Title, Test Step, Acceptance Criteria) all work. You do not need to rename anything.
Before anything is written, the preview tells you what will import, what will be skipped and why (with row numbers), and which IDs already exist and would be overwritten.
Exporting
Export to Excel produces a file in exactly the same layout. That makes bulk editing easy: export, edit fifty test cases in Excel, import back over the top. Re-importing an ID that already exists replaces it.