KhronosGroup / KhronosGroup/SYCL-CTS
Question about test cases distribution between FULL and non-FULL modes
- Dominant language
- C++
- Stars
- 75
- Forks
- 96
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 4
Description
Hi folks,
We have been working on support for SYCL 2020 specialization constants in our SYCL implementation at intel/llvm and we have realized that unless you switch into `FULL` mode, you are missing a huge piece of data type coverage for `test_specialization_constants`. In particular, we do not test `vec` and `marray` data types in non-`FULL` mode at all in those tests.
Therefore, I was wondering if there are some guideline about how CTS should be written to ensure meaningful coverage in both `FULL` and non-`FULL` modes? Do we need to explicitly document the distribution in [test plans](test_plans/)?
Contributor guide
Research direction
Start by reviewing test_specialization_constants in FULL and non-FULL modes, then inspect the related guidance and test plans under test_plans/. The issue does not define a documentation change or an agreed distribution policy; a maintainer decision would be needed before a newcomer could identify the required edits or completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation, testing
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100