Deal with slow staging/sm tests

Open
#4,402 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
testing

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.

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.

Dominant language
JavaScript
Stars
2.9k
Forks
571
Avg merge
1d 22h
Merged PRs (30d)
13

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tc39/test262

All issues in tc39/test262

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.