Skip to main content
Test cases are the individual tests that verify your requirements. Each test case captures the steps to execute, the expected outcome, and metadata like priority and type. Linking test cases to requirements is what drives the coverage matrix.

​
Test case fields

FieldDescription
TitleA short description of what the test verifies
DescriptionOptional context about the test’s purpose
PreconditionsSetup state required before the test can run (e.g., User must be logged in)
StepsAn ordered list of actions. Each step has a Step description, Expected result, and optional Test data
Expected ResultThe overall outcome when all steps pass
PriorityOne of: Critical, High, Medium, Low
TypeOne of: Functional, Integration, E2E, Performance, Security, API, UI
StatusOne of: Draft, Ready, Active, Deprecated
AutomatedCheckbox indicating whether this test is executed by automation
TagsFree-form labels for grouping and filtering

​
Creating a test case manually

1

Open your project's test cases list

Navigate to your project, then click Test Cases (shown as Tests in the sidebar) in the project navigation.
2

Click Create Test Case

Click the Create Test Case button in the top-right corner.
3

Fill in the form

Enter a title. Add one or more test steps — each step has a description, expected result, and optional test data field. Use Add Step to append more steps, and the × button to remove any step (a minimum of one step is required).
4

Set metadata

Choose priority, type, and status. Mark the test as Automated if it is executed by a test runner rather than a human. Add any tags to help with filtering.
5

Save

Click Create Test Case. You are taken to the test case detail page.

​
Importing from AI analysis output

The fastest way to populate a project with test cases is to generate them from your codebase and import them in bulk.
1

Generate tests with AI

From the project overview, click Generate Tests with AI in the Quick Actions panel. This opens the analysis page pre-scoped to your project.
2

Complete the analysis

Select your input method (paste code, fetch from GitHub, or upload files), configure your goal and output format, and run the analysis.
3

Import the results

After the analysis completes, use the Import action to send test cases directly into the project. Orizon creates the test cases and optionally links them to generated requirements in a single operation.
Bulk-imported test cases start with a status of Draft. Review them and change the status to Ready once you have verified they are correct.

​
Filtering and sorting

The test cases list includes a stats bar showing counts by status (Total, Ready, Draft, Active, Deprecated). Click any status pill to filter the list to that status instantly. You can also filter by:
  • Status, priority, type, or automated/manual
  • Free-text search across title, key, and description
Sort by date created, last updated, title, priority, status, or type.

​
Linking to requirements

Open a test case’s detail page to see which requirements it is linked to. You can also manage links from the coverage matrix, which gives you a full view across all requirements and tests at once.
Use type filtering to find all security or performance tests in a project. These are easy to miss in traceability reviews because they often map to non-functional requirements.

​
Running a test case

To execute test cases, go to Runs in the project sidebar and start a new test run. You can select individual test cases or run the entire suite. For browser-based execution of Jest, Vitest, or Mocha tests, see the Browser Runner documentation.