L.O.B.S.T.E.R.

As a requirements manager I want to have a report of traceability between
requirements (in codebeamer or TRLC) and 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 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) covering requirements in (in codebeamer or TRLC).

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
between requirements in codebeamer and C++ tests
to mention the source location of each item.

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,

IF a list element given through the yaml config file option "files" is a file

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.

OTHERWISE IF the file content is invalid,
THEN the tool shall write an error message to stderr
AND exit with a non-zero return code.

This is not really a requirement. It will be used only to generate a minimal tracing report for each tool.
It can be deleted as soon as all the tools get their real requirements.

This is not really a requirement. It will be used only to generate a minimal tracing report for each tool.
It can be deleted as soon as all the tools get their real requirements.