As a requirements manager I want the traceability report to show the list of requirements (from codebeamer or TRLC) which are covered by tests (in C++ or JSON).
As a requirements manager I want the traceability report to show the list of requirements (from codebeamer or TRLC) which are not covered by tests (in C++ or JSON).
As a requirements manager I want the traceability report to show the list of tests (in C++ or JSON) which are not covering any requirement in (in codebeamer or TRLC).
As a requirements manager I want the traceability report to show the fraction of the number of requirements (in codebeamer or TRLC) which are covered by tests (in C++ or JSON) divided by the total number of requirements. The fraction shall be shown as percentage.
As a requirements manager I want the traceability report which includes sources from a local git clone to show the git hashes of the git commit from which files were taken.
As a requirements manager I want the traceability report between requirements (in codebeamer or TRLC) and tests (in C++ or JSON) to show a list with all findings where the tracing policy is violated.
Some requirements are not listed correctly example, - Some requirements which are not covered are not listed in the HTML report. - Some requirements which are covered are not listed in the HTML report.
Some software tests are not listed correctly. example, - Some software tests which are not covering any requirement are not listed in the HTML report. - Some software tests which are covering the requirement are not listed in the HTML report.
Mapping between requirements and software tests is not shown correctly HTML report example, while generating html report rows are interchanged or incomplete data is written in html file.
Syntax of the generated HTML report is not correct example, some content of the report is not readable(e.g. Non readable charachters in lines like string of &,*,.. etc.)
All Tracing policy violations are not listed. example, for software test the requirement reference is missing but tracing policy violation is not detected.
The test shall verify correct tracing policy is mentioned in the HTML report.
example: For requirements in CB and software tests in C++ files, the test shall verify tracing policy between requirements and software tests is correctly shown in the HTML report.
IF the input .lobster file does not exist or is missing, THEN the tool shall exit with a non-zero return code (2) AND shall print an error message to STDERR indicating that the specified file is not a valid file.
IF a valid .lobster file is provided as input, THEN the tool shall execute successfully with a zero return code (0) AND shall write a valid HTML report to the specified output file.
IF a valid .lobster file with MD content is provided as input, THEN the tool shall execute successfully with a zero return code (0) AND shall write a valid HTML report to the specified output file with the rendered MD content.
IF a valid .lobster file containing approximate 20 thousand items is provided as input, THEN the tool shall execute successfully with a zero return code (0) AND shall write a valid HTML report to the specified output file.
IF a valid .lobster file containing a "custom_data" field with keys such as "component", "branch", and "ci_run" is provided as input, THEN the tool shall extract these values from the file AND shall render them in the top-right corner of the generated HTML report AND shall exit successfully with a zero return code (0).
If the input LOBSTER report file contains codebeamer items THEN the generated HTML report SHALL represent these as hyperlinks to the item on the codebeamer server, where the codebeamer server URL is taken from the repo_root configuration parameter.
If the input LOBSTER report file contains codebeamer items THEN the generated HTML report SHALL represent these by their codebeamer item name, if it is given.
The "to_html" method of the Codebeamer_Reference class SHALL return a string representation of an HTML anchor element to the codebeamer item by constructing the URL as follows:
"<repo_roo>/issue/<item_id><version_addon>"
where <repo_root> is taken from the configuration file, and <item_id> is the codebeamer item ID taken from the LOBSTER input file, and <version_addon> is "?version=<version>" IF the version number of the codebeamer item is given, OTHERWISE <version_addon> is an empty string.