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 JSON test files or test cases within JSON files are ignored during extraction. For example, some JSON test files are ignored while extracting reference data.
Some fake requirement references from tests in JSON files are extracted. For example: While extracting requirement references from a test case, an additional reference is considered with partial data from previous requirement reference.
The user does not provide a valid path to a configuration file, but the lobster-json tool generates valid output nevertheless, potentially based on irrelevant JSON files. For example, the lobster-json tool might consider the current working directory as source of JSON 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-json tool generates valid output nevertheless, potentially based on irrelevant JSON 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 JSON 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 a JSON test file, then test shall verify output file contains requirement references 'A' & 'B'.
The test shall verify that the lobster-json tool exits with a non-zero return code when the config file does not exist. Example: Verify that the lobster-json tool throws an error when a non-existent config file is provided.
The test shall verify that lobster-json tool exits with a non-zero return code when the config file contains a syntax error. Example: Verify that lobster-json throws an error when a config file with invalid JSON is provided.
IF the operating system fails to fully serialize the output to a file, THEN the tool shall print an error message to STDERR and exit with a non-zero return code.
Issues:
missing up reference
missing reference to Software Requirements
missing reference to System Tests
Build Reference: main | Timestamp: 2025-09-18 11:06:21+00:00 UTC
IF a list element given through the configuration file under "inputs" is not a file nor a directory, THEN the tool shall exit with a non-zero return code.
In addition to [[Parse_Input_File]], IF the command line option "name-attribute" is given and not an empty string, AND the input items contains that key THEN the tool SHALL use the value of that key as tag in the serialized LOBSTER item.
OTHERWISE ("name-attribute" is not given or not an empty string), the tool SHALL create a synthetic tag name based on the path of the JSON input file and an item counter.
Notes: - "Synthetic" means that, the name does not need to be related to the data. - The item counter does not need to be unique across input files, but it shall be unique at least for each input file separately. - No further specification is made about how to combine the path and the item counter.