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.
Some requirements are not extracted from codebeamer. For example, there are 100 applicable requirements in codebeamer tracker but LOBSTER extracts 75 requirements.
Extra requirements are extracted from codebeamer. For example, there are 100 applicable requirements in codebeamer tracker but LOBSTER extracts 125 requirements with 25 requirements from not applicable section of tracker.
The test shall check that the IDs (including their version) downloaded from codebeamer are exactly the same as written in the output.
Example 1: verify that the tool does NOT truncate IDs. For example, it could download 10 IDs as expected, but those ID strings could be truncated by one digit each.
Example 2: Verify that the tool does NOT duplicate IDs.
Test steps: - download a set of items from a mock server - verify that the obtained IDs are the same as provided by the mock server
IF an element given through the yaml config file option "import_query" is a valid codebeamer query id (integer greater than zero), THEN the tool shall request items from the codebeamer server with the given query id AND write the obtained codebeamer items in the LOBSTER interchange format to the file given in the "out" parameter
IF an element given through the yaml config file option "import_query" is valid codebeamer query string, THEN the tool shall request items from the codebeamer server with the given query string AND write the obtained codebeamer items in the LOBSTER interchange format to the file given in the "out" parameter
IF the actual HTTPS return code is in the list specified by the configuration parameter "retry_error_codes" AND the configuration parameter "num_request_retry" is greater than 0 or not defined, THEN the tool shall retry the request up to a maximum of "num_request_retry" times (default is 5 if not set).
IF the configuration parameter "retry_error_codes" is not defined, THEN the retry logic shall not be executed, regardless of the value of "num_request_retry".
IF an element given through the yaml config file option "refs" is list of codebeamer field names, THEN the tool shall extract the corresponding references from the given codebeamer item fields AND add a Tracing_Tag entry to the LOBSTER item for each referenced item ID