Deal with slow staging/sm tests
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 564
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 10
Description
Some of the staging/sm tests take a long time to run. For this reason the whole folder is currently omitted from test262.fyi. We should find a way to either mark particular tests as slow so that consumers can skip them if necessary, or make them less slow.
See also #3328, #1231.
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 reviewing the staging/sm tests and how test262.fyi currently omits the folder. Read related issues #3328 and #1231 for prior context and constraints. Done means particular slow tests can be skipped by consumers, or the relevant tests no longer require exclusion because their runtime is reduced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100