test: extend skip triage to the remaining ~100 unclassified sites
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8
- Forks
- 1
- Avg merge
- 18h 23m
- Merged PRs (30d)
- 63
Description
#623 triaged eight files (53 sites). Roughly 100 bare pytest.skip() calls remain across src/vip_tests, each still carrying the ambiguous default. Work file by file, adding each to TRIAGED_FILES in selftests/test_skip_triage.py as it is finished, so the guard grows with the coverage.
Highest value first: workbench/test_publish_to_connect.py (12), workbench/test_git_ops.py (10), package_manager/test_binary_packages.py (8), security/test_https.py (4). The security suite deserves care — a check that silently did not run is worse there than anywhere else.
Also settle the three deferred in #623, all previously decided in #268: URL is not HTTPS, tls.insecure=true, No R versions available on Connect. Each is arguably a check that did not happen rather than one that did not apply.
Contributor guide
No contributing guide indexed for this repository
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
Start in selftests/test_skip_triage.py and inspect the remaining bare pytest.skip() calls under src/vip_tests. Work through the named test files first, adding completed files to TRIAGED_FILES, and resolve the three deferred cases using the decisions recorded in #268. Done means the remaining skips have been classified and the guard covers each finished file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100