web-platform-tests / web-platform-tests/wpt
Test the test runner
Open
Nobody has claimed this yet.
infra
priority:backlog
runner
- Dominant language
- HTML
- Stars
- 6.2k
- Forks
- 3.9k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 586
Description
Originally posted as https://github.com/w3c/wpt-tools/issues/145 by @jeremypoulter on 16 Dec 2016, 09:43 UTC:
On a related note to #144 do you have any thoughts on how the test runner could be tested on AppVeyor and/or Travis CI?
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
The issue names no files or tests. Start by locating the test-runner entry point and any existing AppVeyor or Travis CI configuration, then determine how the runner should be exercised in CI. Done would require an agreed, documented approach or implemented CI coverage, but the old unanswered thread provides no settled scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100