As a requirements manager I want the traceability report to show the fraction of the number of items in one level (of the tracing policy) which fulfill the tracing policy, divided by the total number of items in that level (of the tracing policy). The fraction shall be shown as percentage.
Example: If the tracing policy is: Tests --(trace to)--> Requirements, then the report shall show the fraction of requirements which are covered by at least one test, divided by the total number of requirements.
Some non referanced requirement referances from test in c++ file are extracted example: While extracting requirement referances from a test case, an additional referance considered with partial data from previous requirement referance.
The user does not provide a valid path to a configuration file, but the lobster-cpptest generates valid output nevertheless, potentially based on irrelevant C++ files. For example, the lobster-cpptest might consider the current working directory as source of C++ files, and these do in fact contain links to real requirements, such that lobster-report would compute a non-zero coverage value.
The user provides an invalid configuration file, but the lobster-cpptest generates valid output nevertheless, potentially based on irrelevant C++ files. This includes cases where the config file: - contains invalid YAML syntax (e.g., incorrect indentation, missing colons, or other formatting errors), - is missing required keys or attributes,
The test shall verify all the requirement references from all the input files are consumed. The requirements references from all the input files shall be available in the actual output.
example : If a test case contains requirement references 'A' & 'B' in c++ test file, then test shall verify output file contains requirement references 'A' & 'B'.
The test shall verify that the lobster-cpptest exits with a non-zero return code when the config file does not exist. Example: Verify that the lobster-cpptest throws an error when a non-existent config file is provided.
The test shall verify that lobster-cpptest tool exits with a non-zero return code when the config file contains a syntax error. Example: Verify that lobster-cpptest throws an error when a config file with invalid YAML is provided.
AND IF the file content is valid, THEN the tool shall write the output in the LOBSTER interchange format to the file given in the out parameter AND exit with a zero return code.