KhronosGroup / KhronosGroup/OpenCL-CTS
specialization constant tests aren't very complete
Open
- Dominant language
- C++
- Stars
- 232
- Forks
- 235
- Avg merge
- 8d 7h
- Merged PRs (30d)
- 18
Description
Nothing tests any of the failure paths from this.
a test to create an SPIR-V shader, and try and use incorrect sized arguments, incorrect ids,
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files or existing test entry points, so first locate the specialization constant tests and the SPIR-V shader setup. Add coverage for failure paths involving incorrectly sized arguments and incorrect IDs, then verify those tests fail for the intended invalid inputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100