Bug - test-utils.js needs updated when loading .nycrc.yaml files

Abierto
  • ¿Algo no está bien?
#680 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
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
42/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
javascript
Área
testing

Línea de trabajo

Inspecciona test-utils.js y el manejo de los archivos .nycrc.yaml, comenzando por reproducir el fallo de Cypress e2e con la configuración indicada. Verifica que la configuración YAML se cargue correctamente y que los tests de Cypress pasen sin el monkey patch.

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

Descripción

Logs and screenshots
Please provide debug logs by running Cypress from the terminal with DEBUG=code-coverage environment variable set, see the Debugging section of the README file.

Screenshot 2023-08-11 at 8 55 51 AM

Versions

  • What is this plugin's version? If this is NOT the latest released version can you try the latest version, please?
  • If the plugin worked before in version X, but stopped after upgrading to version Y, please try the released versions between X and Y to see where the breaking change was.
  • What is Cypress version? "cypress": "^12.17.3",
  • What is your operating system?
    I tried this locally (latest MacOS) as well as in my ci docker container with the same result:
    cypress/browsers:node16.16.0-chrome107-ff107-edge
    https://github.com/cypress-io/cypress-docker-images/tree/master/included - link to cypress/node images
    image: cypress/included:12.3.0
  • What is the shell? bash
  • What is the Node version? 16.16.0
  • What is the NPM version?
  • How do you instrument your application? Cypress does not instrument web application code, so you need to do it yourself. I do this with webpack config and confirm it works.
  • When running tests, if you open the web application in regular browser, and open DevTools, do you see window.__coverage__ object? Can you paste a screenshot?
  • Is there .nyc_output folder? Is there .nyc_output/out.json file. Is it empty? Can you paste at least part of it so we can see the keys and file paths?
  • Do you have any custom NYC settings in package.json (nyc object) or in other NYC config files. Yes, I use a .nycrc.yaml file.
  • Do you run Cypress tests in a Docker container? Yes, see above info on the docker image for my ci.

Describe the bug
My .nycrc.yaml file is blowing up cypress e2e tests. I have monkey patched test-utils.js to swap out yaml.safeLoad with yaml.load and everything works.

Link to the repo
Bugs with a reproducible example, like an open source repo showing the bug, are the most likely to be resolved.

Example
See #217 that is an excellent bug report example

Lenguaje dominante
TypeScript
Estrellas
440
Forks
114
Merge medio
42 min
PR fusionados (30 d)
19

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

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 cypress-io/code-coverage

Todos los issues de cypress-io/code-coverage

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.