Lobster cpptest requirement input files using trlc #150
Conversation
TannazVhdBMWExt
force-pushed
the
lobster-cpptest-requirement-inputFiles-using-TRLC
branch
3 times, most recently
from
d447366 to
ee8b98d
Compare
lobster/tools/requirements.rsl
Outdated
| ''' String | ||
| } | ||
|
|
||
| type Tool_Requirement { |
There was a problem hiding this comment.
we need the following types:
- System_Requirement
- System_Requirement_Else
- Software_Requirement
Apart from that, feel free to introduce new types like
- Tool_Definition
- Tool_Config_Parameter
TannazVhdBMWExt
force-pushed
the
lobster-cpptest-requirement-inputFiles-using-TRLC
branch
from
6ce6620 to
41f1b71
Compare
TannazVhdBMWExt
force-pushed
the
lobster-cpptest-requirement-inputFiles-using-TRLC
branch
4 times, most recently
from
80cbbb5 to
0670acd
Compare
Detailed requirements for three main scenarios have been added. The related system-tests have been aded.
TannazVhdBMWExt
force-pushed
the
lobster-cpptest-requirement-inputFiles-using-TRLC
branch
from
3428e9f to
c1ba65f
Compare
phiwuu
added
the
internal
| req.Tool_Definition Source_Input_Files { | ||
| title = '''Source input files given''' | ||
| description = ''' | ||
| Valid existing source input files in the case of [[Source_Inputs_Valid]] |
There was a problem hiding this comment.
A question here:
Source_Inputs_Validis given if all input files and directories exist.Source_Input_Filesis given if all input files and directories exist and the files are C++ files. Is this the intention here?
If not, then what is the difference between these two definitions?
There was a problem hiding this comment.
Source_Inputs_Valid is a boolean definition that indicates "is the given input valid?". Thats why we used it in if statement
Source_Input_Files is the file/s themselves if the given input is valid. We used it in the description of our requirement.
| @@ -0,0 +1,587 @@ | |||
| Written 5 lobster items to "cpptest.lobster". | |||
| { | |||
There was a problem hiding this comment.
Does lobster-cpptest really print the output to stdout, too? The config file of this test case specifies an output file.
There was a problem hiding this comment.
Yes. If the config file does not cover all the markers provided in cpp files, the lobster-cpptest tool prints the rest of the markers without references to stdout.
Relevant link
| "tag": "cpp test_case.cpp:TestMacrosTest:3", | ||
| "location": { | ||
| "kind": "file", | ||
| "file": "..\\..\\..\\data\\test_case.cpp", |
There was a problem hiding this comment.
Please use Unix-style forward slashes / instead of Windows-style \\
That is the reason why the test suites are failing (I guess).
Note: The system test framework translates \\ to /, to support running tests on Windows.
| "tag": "cpp test_case.cpp:RequirementTagTest:64", | ||
| "location": { | ||
| "kind": "file", | ||
| "file": "C:\\bmw-software-engineering\\vispiron\\lobster\\tests-system\\lobster-cpptest\\data\\test_case.cpp", |
There was a problem hiding this comment.
Absolute paths won't work when running in the CI.
|
Please have a look at #157. That PR introduces a possibility to run system tests where the generated *.lobster file contains absolute paths. |
No description provided.