Description
Tests capture verification and validation activities that provide evidence a system meets its requirements. A Test can represent a physical or software test, analysis, inspection, demonstration, or milestone review, based on its project-defined category. Tests complement Requirements: requirements describe what the system must satisfy, while tests define the activity and evidence used to verify it. Link a Test to the requirement it verifies using averify relationship.
Test Hierarchy
Tests can contain child Tests. A leaf Test records its own result and verdict. A parent Test rolls up the verdicts of its children according to the category’s configured rollup mode.
Parent rollups use the numeric scores assigned to each category verdict. The selected category determines how those child scores become the parent’s verdict.
Evaluation
A leaf Test evaluates one observed result against its evaluation criteria:- Define the expected observation type in Results Value: number, text, or boolean.
- Provide the observed value directly or calculate it with an equation or reference.
- Map result ranges or values to named verdicts in Evaluation Criteria.
- The Test resolves to the matching category verdict.
Results Value is the observed measurement or assessment. Resolved Value is the normalized score for the selected verdict, such as
1 for Pass or 0 for Fail. They are not the same value.Evaluation State
Running a Test executes its configured procedure when applicable, records the resulting evidence, and updates its evaluation state. Equation-based results can also update a verdict live as referenced model values change.
Categories and Verdicts
Each Test uses a category configured in the project’s Test Categories settings. A category defines the available verdict names, colors, normalized scores, and parent rollup mode. New projects include categories for Test, Analysis, Inspection, Demonstration, and Milestone Review. The first four typically use Pass and Fail verdicts; Milestone Review includes readiness verdicts such as Go, Conditional Go, and No-Go. Projects can customize these categories and verdicts to match their verification process.Rollup Modes
New projects use Weighted for Test, Analysis, Inspection, and Demonstration categories. Milestone Review uses Minimum so the least-ready review area controls the overall outcome.
View Types
Properties Fields
Name of the object.
Short name of the object.
Description of the object.
The project-defined verification method used by this Test. The selected category determines the available verdicts and rollup behavior.
Tracks the activity lifecycle:
pending, started, done, cancelled, or waived.The Test’s relative contribution to a parent verdict when the category uses Weighted rollup. It does not affect All or Minimum rollups.
Describes how to perform the Test and can reference documents, code, actions, or other model objects that contain the procedure.
Defines the observed number, text, or boolean result. It may be entered directly or calculated from equations and model references.
Maps possible observed results to category verdicts. For numeric results, criteria can include target expressions and display units.
Describes the completed evidence and can reference result artifacts, documents, code, or other model objects.
The resolved category verdict for a leaf Test, or the rolled-up verdict for a parent Test.
A list of all child Test objects owned by this Test.Child Tests can be viewed and deleted, and their verdicts roll up into this Test.Read more about TestsTests that must be completed before this leaf Test can proceed.
Connects the Test to requirements it verifies and to other model objects.Read more about Relationships