With TEST-GUIDE you can plan test case coverage in detail, release by release. Associated requirements, conditions, variants and results remain transparent and traceable at all times.
The crux of any release or sub-release is the question: Have all the necessary and planned test cases been executed? Coverages help answer this question. They instantly indicate the level of test case coverage for specific requirements, parameter ranges, or variants. A quick, trained look is often all that is needed to correctly evaluate the test results in the graphs and tables.
Coverages are defined using coverage filters. These filters define the boundary conditions for the test scope of a requirement, for example, the vehicle variant or engine class which is to be tested. For a quick start, prefabricated examples are already available that you can customize.
Filters can be imported to TEST-GUIDE from files and ALM systems (e.g., Polarion, HP-ALM, Octane), as well as automated via the REST API, e.g., for Continuous Integration solutions.