Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

a way to merge reports from multiple node versions?

Aperta
  • Qualcosa non va?
#3,680 7 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
28/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
html, javascript, node.js
Ambito
testing, tooling

Direzione di ricerca

The request is to merge mutation-testing reports from different Node versions the way coverage files are merged after CI, so a mutant only counts as survived if it survived in every input. Start from the schema and report format this repo defines for mutation results and how the web components consume them. Done looks like a documented merge step (or API) that combines multiple report files into one final report.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

Is your feature request related to a problem? Please describe.
Specifically, I have lots of packages that do feature-detection - something that, eg, works in node 20 and not in node 18 - and so running the tests in node 20 won't "survive" mutation of that feature-detection precisely because it would require the older engine to test.

If I run the tests in node 18, then a different complementary set of code will "survive" mutation.

Describe the solution you'd like
This problem occurs in code coverage as well, and the industry-wide solution there is to generate coverage reports as files on disk, and then to merge those after CI is done, and then report on the final result - meaning, in order for a mutation to have "survived", it has to have done so in every input to the merged final report.

Describe alternatives you've considered
Asking for the ability to have "ignore mutation" comments or similar; manually ignoring results I know aren't a problem; or not using this mutation approach at all.

Additional context

[Survived] ConditionalExpression
index.js:1:14
-   var hasMap = typeof Map === 'function' && Map.prototype;
+   var hasMap = true;

in an engine without native Map, this mutation will fail a great many tests; but in an engine with it, it will survive. This should not be reported, as long as I'm able to run the mutation on a node version without Map (or, as long as I'm able to run a "preamble" that deletes Map before running the tests and mutations).

Lingua principale
HTML
Stelle
29
Fork
21
Merge medio
7h 7m
PR unite (30g)
27

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di stryker-mutator/mutation-testing-elements

Tutte le issue di stryker-mutator/mutation-testing-elements

Issue simili

Altre issue su Testing & QA

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.