High Impact Suggestions for the Team

Ouverte
  • Quelque chose ne va pas ?
#21 6 commentaires 9 réactions 0 personnes assignées Voir sur GitHub

@vassudanagunta y travaille déjà.

Depuis le 7/3/2026.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
18/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
À l'abandon
Stack technique
javascript, node.js
Domaine
developer-experience, testing-qa, tooling

Piste de recherche

Start by separating the proposed work into the linked coverage, npm scripts, console output, and module mocking issues, then review the referenced Console implementation and pull request. The issue has no single entry point or acceptance criterion; each proposal would need its own scope, design, and definition of done.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

test_runner-agenda

Hi Test Runner Team,

I realize that everyone here is a volunteer and contributes whatever they want (or doesn't even contribute at all). There are some issues that I think may be flying under your radar that I think could have a big impact on the test runner experience:

  • Finish/stabilize code coverage. I've seen this in use a fair amount in the wild, but people always point out that it is still experimental. I think it's worth evaluating the accuracy and considering stabilizing it. The performance would also be good to look at, but should not be considered a blocker since it can be improved without impacting users. Coverage also does not support statement level coverage, but this should not be a blocker because:
    • This is an artifact of V8's coverage output. Outside of changing V8, getting statement level coverage would require an additional parsing pass over all of the source code to map statements to positions in files. This would almost certainly be bad for performance.
    • I believe C8 also does not support statement coverage for V8 output. My understanding is that line coverage is reported as statement coverage because it's good enough.
    • It can always be added in a semver minor change if someone comes up with a good solution.
  • Combining test runner flags with npm scripts (https://github.com/nodejs/node/issues/51384) - There are some possible solutions described in that thread. Right now, it's possible to work around this with NODE_OPTIONS, but it's not really a nice solution. That issue appears to be a blocker to jsdom adopting the test runner for example. This would be a massive DX improvement.
  • Properly associating console.log() output with its test in the reported output (https://github.com/nodejs/node/issues/53103) - One way to solve this could be to add code to Console, similar to what diagnostic channels do. Then, that code could integrate with the test runner's reporter functionality. This would be a massive DX improvement.
  • Stabilize module mocking. If https://github.com/nodejs/node/pull/61767 lands, I think it would make sense to leverage that first. I wanted to do something similar when I originally wrote the mocking code, but I anticipated there being FAR more pushback on breaking spec compliance then there has been in #61767. For ESM in particular, #61767 has the potential to greatly improve the DX of module mocking.

Some other nice to have changes would be:

  • Migrate the test runner off of async_hooks. Now that AsyncContextFrame, it may be possible to achieve the same functionality, and I believe the project would like to get rid of async_hooks. Currently, async_hooks are only used to map asynchronous activity back to the test that initiated it. I haven't investigated what it would take to make this change in much detail.
  • Give the spec reporter a new paint job. As long as you don't change the programmatic behavior of the reporter, we are free to change the actual output (text, colors, etc.) of the reporters without regard for semver. This has the potential to be a big DX improvement.
Langage dominant
Aucune donnée de langage
Étoiles
3
Forks
4
Aucune PR mergée en 30 j

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de nodejs/test-runner

Toutes les issues de nodejs/test-runner

Issues similaires

Plus d'issues DevTools

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.