testing: add first component integration test to baselib#51
testing: add first component integration test to baselib#51PiotrKorkus wants to merge 1 commit intoeclipse-score:mainfrom
Conversation
initial version of CITs for baselibs
PiotrKorkus
requested review from
4og,
LittleHuba,
castler,
hoe-jo,
nradakovic and
ramceb
as code owners
|
The created documentation from the pull request is available at: docu-html |
|
|
||
|
|
||
| @add_test_properties( | ||
| partially_verifies=["comp_req__json__deserialization"], |
There was a problem hiding this comment.
This seem to be the only requirement mentioned for the testing.
If it is just a test which applies to partially address a single component requirement the Pull Request may require to be named differently to "testing: add first component integration test to baselib"
There was a problem hiding this comment.
Correct, this is initial version. I focused on making everything work rather than test implementation
PiotrKorkus
changed the title
There was a problem hiding this comment.
Only checked scope and that tests have a trace using described methods.
Improvement point is to improve the language of the test case descriptions/specification to indicate more clearly what it does, expected output, etc.
As this is the initial commit to "have something working". It is sufficiently described.
(Note: Functional check and integration was not performed)
4og
left a comment
4og
left a comment
There was a problem hiding this comment.
Hi @PiotrKorkus, could you help me understand the benefits of CITs over plain Google Tests? Since the baselibs consist of cc_library targets, they can easily be tested with Google Tests without the added complexity Python tooling of CIT.
3 participants
initial version of CITs for baselibs