Harness tests should run when harness source changes
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 564
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 10
Description
#4197 notes that #4091 and #4187 broke some harness tests, which should have been surfaced sooner. I think we should update the package.json test:diff:… scripts to include all test/harness/*.js files whenever harness/ includes any changes.
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
Start in package.json by reading the test:diff:* scripts, then inspect the harness/ and test/harness/*.js paths mentioned in the issue. Update the scripts so harness tests run when harness sources change, and verify the diff-test commands cover those cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100