> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dalus.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Test Cases
> Plan, execute, and track verification and validation tests for your system.
The Test Cases page helps you manage your verification and validation activities. Define test procedures, schedule executions, record results, and trace tests back to requirements and system components.
## Accessing Test Cases
Open the Test Cases page from the left sidebar. The page displays all test cases with their status, and you can switch between list view and timeline view.
## Creating a Test Case
1. Click **New Test Case** to create a new test record.
2. Enter a descriptive name (e.g., "Thermal Cycling Test" or "EMI Compliance Check").
3. Add a detailed description of the test objectives.
Each test case automatically receives a sequential ID (TE-1, TE-2, etc.) for traceability.
## Test Case Properties
### Status
Track execution progress:
| Status | Meaning |
| --------------- | ------------------------------------ |
| **Planned** | Scheduled and ready to execute |
| **In Progress** | Currently being executed |
| **Passed** | Met all acceptance criteria |
| **Failed** | Did not meet criteria |
| **Blocked** | Cannot execute due to external issue |
### Lifecycle Status
Track the test definition maturity:
| Status | Meaning |
| -------------- | ------------------------- |
| **In Work** | Test case being developed |
| **In Review** | Under review for approval |
| **Baselined** | Approved and locked |
| **Deprecated** | No longer active |
### Purpose
Why is this test being conducted? Select one or more:
| Purpose | Description |
| -------------------- | --------------------------------------------- |
| **Validation** | Confirm the right product was built |
| **Verification** | Confirm product meets requirements |
| **Risk Mitigation** | Reduce identified risks |
| **Characterization** | Understand system behavior |
| **Certification** | Meet regulatory or certification requirements |
| **Defect Detection** | Find defects and bugs |
### Type
What kind of test is this?
| Type | Description |
| -------------------- | ---------------------------------------------- |
| **Functional** | Functional verification testing |
| **Acceptance** | Customer or user acceptance testing |
| **End-to-End** | Full system integration testing |
| **Environmental** | Environmental condition testing |
| **Thermal Vac** | Thermal vacuum testing |
| **Vibration** | Vibration testing |
| **EMI/EMC** | Electromagnetic interference and compatibility |
| **Drop** | Drop and shock testing |
| **Software-in-Loop** | Software-in-the-loop simulation |
| **Hardware-in-Loop** | Hardware-in-the-loop simulation |
| **Other** | Custom test type (specify in description) |
## Scheduling
Plan when and where tests will occur:
* **Date** — Scheduled execution date
* **End Date** — For multi-day tests
* **Time Window** — Specific time slot (e.g., "09:00-12:00")
* **Facility** — Test location or lab name
## Test Procedure
Define step-by-step instructions for executing the test.
### Adding Procedure Steps
1. Click **Add Step** in the procedure section.
2. Enter a clear step title describing the action.
3. Add the expected result for this step.
Write comprehensive procedures with 4-10 steps covering setup, execution, verification, and cleanup phases. Clear procedures improve test repeatability.
## Test Runs
Record each execution of a test case. A single test case can have multiple runs (e.g., retests, different configurations).
### Starting a Run
1. Click **+ New run** to create a new execution record.
2. The run starts in **Scheduled** status.
3. Execute the procedure steps, marking each as Pass or Fail.
4. Update the run status as you progress.
### Run Status
| Status | Meaning |
| --------------- | -------------------------------------------- |
| **Scheduled** | Run planned but not yet started |
| **In Progress** | Run currently executing |
| **Passed** | All steps passed |
| **Failed** | One or more steps failed |
| **Blocked** | Run could not complete due to external issue |
### Recording Step Results
For each procedure step in a run:
* Click **Pass** or **Fail** to record the result
* The progress indicator updates automatically showing pass/fail/pending counts
* Each step shows its title and expected result for reference
### Run Attachments
Add supporting documentation to each run:
* Click **Add link** to reference external resources
* Click **Upload** to attach files directly
* Attach test data, photos, logs, or anomaly reports
## Traceability
### Systems Under Test
Link test cases to the Parts being tested. This shows which components are covered by testing and helps identify gaps in test coverage.
### Requirements
Link requirements that this test verifies. For each linked requirement, add a rationale explaining how the test addresses the requirement.
## Views
### List View
The default view shows test cases as a sortable, filterable list with:
* Test case ID and name
* Status badges
* Type and purpose
* Scheduled date
* Quick actions
### Timeline View
Switch to timeline view to see tests on a calendar:
* Visual schedule of planned tests
* Multi-day tests shown as spans
* Drag to reschedule (when editing is enabled)
* Color-coded by status
## Filtering and Search
Use the filter bar to narrow the list by:
* **Status** — Planned, In Progress, Passed, Failed, Blocked
* **Type** — Functional, Environmental, etc.
* **Purpose** — Verification, Validation, etc.
* **Lifecycle Status** — In Work, In Review, Baselined, Deprecated
* **Systems** — Filter by systems under test
* **Date Range** — Filter by scheduled date
* **Facility** — Filter by test location
Search by test case name or ID using the search bar.
## Grouping and Sorting
Organize the test list by:
* **Group by**: None, Status, Type, or Purpose
* **Sort by**: Name, Date, Status, or Type
## Exporting Test Reports
Generate documentation for reviews and audits:
1. Select test cases to include (or export all).
2. Click **Export Report**.
3. Choose export options and metadata.
4. Download the generated report.
Reports include test details, procedures, run results, and traceability information.
## Best Practices
1. **Write clear objectives** — Each test should have a specific, measurable goal.
2. **Define acceptance criteria upfront** — Know what "pass" looks like before you test.
3. **Include expected results in procedure steps** — Make it easy for anyone to execute the test and evaluate results.
4. **Link to requirements** — Maintain traceability so you can demonstrate test coverage.
5. **Record everything** — Attach evidence, note observations, and document any anomalies.
6. **Review before baselining** — Use lifecycle status to control test case maturity.
## Permissions
Test case management respects model permissions:
| Role | Can Create | Can Edit | Can Delete |
| ---------- | ---------- | -------- | ---------- |
| **Owner** | ✓ | ✓ | ✓ |
| **Admin** | ✓ | ✓ | ✓ |
| **Editor** | ✓ | ✓ | ✓ |
| **Viewer** | — | — | — |
Viewers can browse test cases and runs but cannot modify them.