web-platform-tests / web-platform-tests/wpt
timeout_multiplier property on setup does not apply to all tests
Nobody has claimed this yet.
- 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/testharness.js/issues/204 by @halindrome on 17 Jul 2016, 15:07 UTC:
The timeout_multiplier property is applied to each test step and each Test, but not to the timeout of the overall Tests object.
See Tests.prototype.set_timeout()
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
Locate Tests.prototype.set_timeout() in the testharness.js implementation and trace how timeout_multiplier is applied to individual tests and steps. Update the overall Tests timeout behavior so the multiplier applies there too, then run the relevant testharness tests to confirm all timeout levels are handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100