tests: posix: ensure each testsuite has at least one integration platform #86633
Labels
area: POSIX
POSIX API Library
area: Tests
Issues related to a particular existing or missing test
Enhancement
Changes/Updates/Additions to existing features
Is your enhancement proposal related to a problem? Please describe.
There are too many QA issues with POSIX testing. The primary one being that there are no dedicated integration platforms. This can result in slow CI times.
Describe the solution you'd like
We should probably add one common integration platform per testsuite.
The other QA issue is that there are too many scenarios. However, those scenarios are necessary to ensure that we have coverage across the necessary libc's.
Describe alternatives you've considered
I was under the impression that testing on all tier0 targets was sufficient (and also ideal) in that it would result in fewer regressions.
However, if that's not the case, then we'll add 1 integration platform if one does not already exist.
One thing that isn't clear to me is whether QA considers the
platform_key
permutations when it reports on missingintegration_platforms
. From what I understand, usingplatform_key
to run tests for each major architecture in simulation should give sufficient coverage to ensure that there are no regressions.I have some concerns that adding 1 integration platform might skip tests that are otherwise necessary to ensure that we don't see regressions due to missing coverage.
Additional context
Output of
./scripts/twister -ll qa -y -T tests/posix/
using theqa
tag from #86571The text was updated successfully, but these errors were encountered: