Test cases are reusable test specifications that form the foundation of your testing in ISO Mate. Each test case holds ordered steps, properties such as priority and type, and links to the requirements and defects it relates to. You create and organize them from the Test Cases page in the Quality Assurance group.
Create a test case
- Open the Quality Assurance group in the sidebar and select Test Cases.
- Use the Create button. When AI create is enabled for your account, Create with AI can draft the test case from a short prompt.
- Enter the title and an optional description.
- Set the properties: priority (Critical, High, Medium, Low), type (Functional, Regression, Smoke, Integration, Acceptance, Performance), status (Draft, Ready, Deprecated), and complexity (Simple, Medium, Complex).
- Add preconditions describing what must be true before the test runs, and an estimated duration in minutes.
- Optionally assign the test case to a folder.
- Save the test case.
Add test steps
Steps define what the tester does and what should happen. Each step captures an action, an expected result, and optional test data.
- Open a test case and go to the Test Steps section.
- Use Add Step and enter the action, the expected result, and any test data.
- Steps are numbered in sequence automatically.
- Reorder steps by dragging them, and duplicate a step to build similar ones quickly.
Organize with folders
The folder sidebar groups test cases by module, feature, or any structure your team prefers. Create root folders and nested subfolders, then assign a test case to a folder from its form.
Versioning, cloning, and dependencies
Version history
When you update a test case, a new version is created and the previous version is preserved. Review the full history from the Version History tab on the test case detail page, and revert to an earlier version when needed.
Cloning
Clone a test case to create a variation. The clone copies all fields and steps so you only change what differs.
Dependencies
Define dependencies between test cases from the Dependencies tab to establish execution order, so testers know which case must run first.
Parameters for data-driven testing
Add parameters to a test case from the Parameters tab, then define parameter sets with different value combinations to run the same test case with varied data.
Link to requirements and defects
From the test case detail page, link user stories and acceptance criteria for requirements coverage, and link issues for defect traceability. The Execution History tab shows every time the test case has been run across your test cycles.
Work in bulk
Select several test cases to delete them together. Use the filters and folder sidebar to narrow the list before you act.
Build test cases from an AI assistant
Everything on this page can also be driven over the MCP server, so a connected AI assistant can build a test case library without anyone opening the console. It can create a test case with all of its steps in a single request, then add, edit, reorder, duplicate, and delete steps afterwards. It can read the folder tree and create, rename, move, or delete folders, so cases are filed as they are created rather than piling up unfiled. It can also link a case to a user story or to an individual acceptance criterion, which is what gives you real coverage in the traceability matrix.
See Connecting via the MCP Server for how to create a scoped token and connect your tool.
New to ISO Mate? Every account starts with a 14-day free trial.