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.
If no input files are specified, the tool might inadvertently use the current working directory (or any other default value for these configuration parameters) as the location to search for input files.
Some TRLC requirements are not extracted from TRLC files. For example, there are 100 applicable requirements in TRLC files but LOBSTER extracts only 75 requirements.
The user does not provide a valid path to a configuration file, but the tool generates valid output nevertheless, potentially based on irrelevant input files. For example, the tool might consider the current working directory as source of input files, and these do in fact contain links to real other items, such that lobster-report would compute a non-zero coverage value.
The user provides an invalid configuration file, but the tool generates valid output nevertheless, potentially based on irrelevant input 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 that the extracted data is consistent with the input data according to the configuration.
For example, the input may contain 5 items of type "Information" and 6 items of type "Requirement". The configuration specifies to extract only "Requirement" items. The test needs to verify that these 6 requirement items are consistent with the LOBSTER output.
The test shall verify that the lobster-trlc tool exits with a non-zero return code when the config file does not exist. Example: Verify that the lobster-trlc tool throws an error when a non-existent config file is provided.
The test shall verify that lobster-trlc tool exits with a non-zero return code when the config file contains a syntax error. Example: Verify that lobster-trlc throws an error when a config file with invalid TRLC is provided.
The test shall verify that lobster-trlc tool exits with a non-zero return code when the config file contains conversion rules for TRLC record types which do not exist in the RSL file.
IF the list elements given through the config option "inputs" are files with extension rsl and trlc, THEN all files given in "inputs" parameter shall be consumed.
IF the element given through the config option "inputs_from_file" is a file, THEN each line in that file shall be interpreted as a path AND shall be consumed.
IF both the config options [[Input_List_Of_Files]] AND [[Inputs_From_File]] are provided, THEN all files given in [[Input_List_Of_Files]] AND [[Inputs_From_File]] parameter shall be consumed.
IF both the config options [[Input_List_Of_Files]] AND [[Inputs_From_File]] has duplicate definitions, THEN "duplicate_definition" error must be produced.
If a output file is specified as command line argument, then the output must be written into that file. Otherwise, the output shall be written to 'trlc.lobster'.