For requirements 'Properties' view contains four tabs:
For test purposes 'Properties' view contains four tabs:
For reports 'Properties' view contains two tabs:
Template – a template which form and content defines how the report looks like and what data it contains. For example, data can be represented as a list or a table. Also report could include all nodes of the Requirements tree or only nodes of some specific type. In the case of plug-ins for Requality, list of available templates can be expanded. You can create required templates by yourself. The template could be changed manually: just select it in the list of the possible templates. Three templates are available by default: 'XML-export', 'Requirements Coverage' and 'Test Purposes Coverage'. List of available templates could be expanded if you add your own templates or use additional plug-ins for Requality.
'XML-export' - a report in XML, is designed to use Requality reports by other tools.
'Requirements Coverage' – contains list of all requirements.
'Test Purposes Coverage'- contains statistics about requirements and test purposes statuses, and also contains table of all the requirements and test purposes.
ATTENTION! The feature is experimental. It can be changed in further releases.
a file in XML format with the following structure:
<?xml version="1.0" encoding="UTF-8"?> <coverageInfo> <reqcoverage qid="unique_identifier_of_requirement_or_test_purpose"> <covered_by uri="path_to_covering_element" hits="1"/> </reqcoverage> </coverageInfo>
Description.
File has only coverageInfo element containing one or more reqcoverage elements.
There is a reqcoveragefor each covered requirement or test purpose. Not covered items are not described.
Element reqcoverage may contain one or more covered_by elements(one for each test).
Attribute hits is optional, it is contains a number of checks of the requirement by the test.
unique_identifier_of_requirement_or_test_purpose - is user-visible-name(element) or qualifying-id(element) of covered item
user-visible-name(element) - is name of the element, if it has it (that means that field name in Properties view for this element is not empty), otherwise it is user-visible-name(element.parent)/id, that means user-visible-name of parent element with id - identifier of element (separator character is '/'). For example: "TR-FMF-01-01-002/TR-FMF-01-01-002_T01"
qualifying-id(element) - is a full path to the element starting from the root element (Requirements) with separator character '/'. For example: "Requirements/01/MyRequirement01"
path_to_covering_elementa path to test with optional line number, for example: "file:///home/user/work/test1.c#12"
automatic search of files containing identifiers of requirements or test purposes covered by that files
in this case Requality performs search over user-selected projects in current workspace looking for files with user-selected extension. For found files it is performed line-by-line check over its content by regular expression defined by user. As a result, a set of covered elements and related covering files is collected.