Create separate application for integration tests#389
Conversation
|
Looking at the amount of code added here this seems to do a lot more than "grouping tests". |
|
@christian-schilling The commit message is updated with relevant information regarding the PR. @amit-warbhe Could you please confirm? |
nemadhu
changed the title
The rationale behind creating a separate executable for integration test was to conserve hardware resources, such as GPIOs, and prevent them from being unnecessarily occupied. |
rolandreichweinbmw
force-pushed
the
cr-165631
branch
from
40d3503 to
1193c6f
Compare
|
@nemadhu : Please update the branch including treefmt and copyright header checks. |
|
@nemadhu , @amit-warbhe please update this branch. There are several failing checks. |
nemadhu
force-pushed
the
cr-165631
branch
3 times, most recently
from
5c972e7 to
8ebcbac
Compare
- Creates an integrationTestApp executable with slightly different configuration compared to refApp. - The purpose is limited to perform integration tests, not for documentation or demo. - Currently integrationTestApp uses a pin assignment which is conflicting to the existing pin assignement in refApp and test/pyTest/console/test_pwm.py test is performed on s32k148 target, but more tests can be added. - Group tests based on the target elf. Tests can be performed on refApp and integrationTestApp. /testconfig folder is added where targetelf_tests.toml can be created or updated to group test cases - Fix formatting check errors
5 participants
Group tests based on the target elf
/testconfig folder is added where targetelf_tests.toml can be created or updated to group test cases