oracle-gaps: mutant copies resolve bare imports from --package, not from the original file (288 setup-errors)

Abierto
#68 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
40/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript

Línea de trabajo

Start at check.mjs near line 1007, where mutant copies are said to resolve imports like the original file, and at the wrapper plugin's resolveId and load hooks that serve those copies. Reproduce by running oracle-gaps against the tests/realtime-oracles oracle file, which should fail with 'Cannot find package fast-check'. Done means copies resolve bare imports from the original file's directory or baseline refuses early, and setup errors are excluded from the gap count and get their own directive.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Reported from an adopter's first session, at c58b0c2. Not yet reproduced here.

Problem. 288 of 388 mutants were setup-error: "Cannot find package 'fast-check' imported from tests/realtime-oracles/src/.oracle-gaps-5482-10-ordered-live-results.oracle.test.ts". The baseline loads the same import from tests/realtime-oracles/node_modules/fast-check. The comment at check.mjs:1007 says copies are placed beside the file "so that its imports resolve as the file's do". But the copy is virtual: the wrapper plugin serves it through resolveId and load. So its bare imports seem to resolve from --package, the repo root, which has no fast-check.

Two more problems follow from that:

  • setup errors count toward the headline gap count, which came out as 307 gaps;
  • they get the directive "Run an owner test that loads this module", which doesn't apply.

Proposal.

  • Resolve a copy's imports from the original file's directory. Alternatively, refuse at baseline when the oracle file's imports don't resolve from --package.
  • Either way, keep setup errors out of the gap count. A harness failure stops the run and is never charged to a mutant (decision LA-v20-1, cleanup plan Phase 2 A2). Give them their own directive.

This issue was written by Isaac.

Lenguaje dominante
JavaScript
Estrellas
5
Forks
1
Merge medio
8 h 31 min
PR fusionados (30 d)
60

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TanStack/oracles

Todos los issues de TanStack/oracles

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.