This repository was archived by the owner on Jul 21, 2021. It is now read-only.
This repository was archived by the owner on Jul 21, 2021. It is now read-only.
Define integration test framework #17
{{ message }}
Thursday Aug 08, 2019 at 11:43 GMT
Originally opened as https://github.com/Bosch-AE-SW/cddk-oss/issues/193
Define and agree on integration test framework e.g.
how to test SPI on different boards (with different MCUs) --> this is only a planning (evaluation) and not a doing
==> MCU loopback
where to store the integration tests? --> part of code repo, documentation of integration tests tbd. (Hugo or markdown in code?), results accessible via Jenkins
==> essentials\test\integration\specs
==> ref HW (board) integration test spec not defined, yet
==> Jenkins not defined, yet
Reuse existing integration test framework --> as a start (due to critical project status right now)
==> added testing to core #105
Make integration testing public or not? --> yes, see G1 slides "Whats part of CDDK open source"
Info: strong interest of AWS on that vs. benefit for other Bosch parties (e.g. PS with OEMs) to re-use and run own integration tests.