Getting Started Overview
This section walks you through the core concepts of TESTMETRIX and how to set up your first complete testing workflow.
Core Concepts
Projects
A project in TESTMETRIX maps to a firmware product or a subsystem under test. Each project has its own:
- Test case library
- Test runs and history
- Coverage reports
- Team members and permissions
Test Cases
A test case is a documented procedure that verifies a specific behavior of the system under test. Each test case includes:
| Field | Description |
|---|---|
| Title | Short, descriptive identifier |
| Description | What the test does and why |
| Preconditions | Required hardware/software state before running |
| Steps | Step-by-step execution instructions |
| Expected Result | What a successful outcome looks like |
| Category | Module or functional area |
Test Runs
A test run is a concrete execution of one or more test cases, associated with a specific firmware build or version. Test runs capture:
- Which test cases were executed
- The result (pass / fail / blocked / not run)
- Observations and attachments
- Duration and timestamps
- The tester who executed the run
Coverage
Coverage in TESTMETRIX tracks what percentage of your defined test cases have been executed and passed for a given firmware version. It is requirements-level coverage, not code coverage.
Recommended Workflow
1. Define project
│
▼
2. Author test cases (linked to requirements if available)
│
▼
3. Create test run for firmware build X.Y.Z
│
▼
4. Execute tests (manually or via API)
│
▼
5. Review results & coverage report
│
▼
6. File defects for failures → retest in next build