Re-enable custom_operation test in nvqc_regression_tests.yml when server supports it
Open
Nobody has claimed this yet.
stale-notified
testing
- Dominant language
- C++
- Stars
- 1.1k
- Forks
- 456
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 165
Description
Required prerequisites
- Search the issue tracker to check if your feature has already been mentioned or rejected in other issues.
Describe the feature
Custom operations are new feature planned for 0.8, and as such any NVQC regression tests that attempt to exercise this will fail. Hence, we will disable it now, and open this issue to track when to re-enable it. It will be re-enabled once the deployed NVQC servers support it (near the time when 0.8.0 is officially released).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open nvqc_regression_tests.yml and locate the disabled custom_operation test. First verify that the deployed NVQC servers support custom operations, then re-enable the test and run the NVQC regression suite to confirm it passes.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100