Typical Workflow
This page describes what a typical and complete workflow with TESTMETRIX® looks like – from the initial setup to the analysis of test results.
Step-by-Step Overview
1
Create Project
The project forms the top-level organizational unit and serves as a container for all further data such as pipeline runs, test runs, and test artifacts
Learn more →2
Create Verification Project
Create a verification project to structure requirements and test cases
Learn more →3
4
Create Test Case Project
Create a test case project, define initial test cases and specify which requirements are covered.
Learn more →5
Create Pipeline Definition
Create a pipeline definition for the type of pipeline you want to run – e.g. a Nightly Pipeline, Post-Commit Pipeline, etc.
Learn more →6
Run Tests
Run your tests. TESTMETRIX® is framework-agnostic – as long as a JUnit XML report is generated, the subsequent upload works
7
8
Upload Test Run
Upload the JUnit XML report and assign it to the appropriate pipeline run.
Learn more →9
Adjust Test System Configuration
Enter the actually used software versions of the DuT and test system components into the test system configuration.
Learn more →10
Upload Test System Configuration
Upload the test system configuration and link it to the corresponding test run.
Learn more →11
Upload Recorded Metrics
Upload metrics either at test run or test case level, depending on the desired context.
Learn more →12
Analyze Results
Open TESTMETRIX® and analyze the test results. Compare test runs, identify trends, and find root causes faster.
info
Steps 1 to 5 are typically performed via the user interface, as they are carried out infrequently. Steps 6 to 12 are typically automated via the REST API.
Was this page helpful?