test262 coverage gap in `ValidateTemporalUnitValue`
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3.7k
- Forks
- 177
- PR merge metrics
- No merged PRs in 30d
Description
I modified temporal-polyfill-lite code and made it throw TypeError instead of RangeError when rejecting auto option, but the modified polyfill (which is incorrect) still passed all test262 cases.
It suggests that behavior of rejecting auto is not fully covered in test262.
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 by locating the test262 cases covering ValidateTemporalUnitValue and inspect how rejection of the auto option is tested. Add coverage that distinguishes the required error type from the incorrect TypeError behavior, then run the relevant test262 cases to confirm the modified polyfill no longer passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100