Coverage is not working with 'cypress' in project path

Aperta
  • Qualcosa non va?
#726 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
38/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
cypress, typescript
Ambito
testing, tooling

Direzione di ricerca

Riproduci il problema nel progetto angular-library-cypress collegato eseguendo npm run cypress-project-run da un percorso contenente cypress, quindi ripeti da un percorso rinominato. Inizia dalla sezione Debugging di README e dal codice che crea o individua .nyc_output/out.json; il lavoro è concluso quando la coverage funziona indipendentemente dal nome del percorso del progetto.

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

Descrizione

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.

Exception in output that coverage could not be found

2023-11-12 12:03:29: webpack compiled in 8669 ms (c571cd78cb7c28bd)


  NgButtonComponent
Cannot find coverage file C:\Daten\jNetwork\angular-library-cypress\.nyc_output\out.json
Skipping coverage report
    √ should click (375ms)

Versions

  • What is this plugin's version? If this is NOT the latest released version, can you try the latest version, please?

3.12.9

  • 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.

no

  • What is the Cypress version?

13.5.0

  • What is your operating system?

Windows 10

  • What is the shell? -

windows cmd

  • What is the Node version?

v16.15.1

  • What is the NPM version?

8.12.2

see in my example projcet

  • When running tests, if you open the web application in a regular browser and open DevTools, do you see window.__coverage__ object? Can you paste a screenshot?

problem can be reproduced with my example project

  • Is there a .nyc_output folder? Is there a .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?

no. folder is not written

  • Do you have any custom NYC settings in package.json (nyc object) or in other NYC config files?

no

  • Do you run Cypress tests in a Docker container?

no

Describe the bug

If the name Cypress is present in the project path, Code Coverage does not work. The output Cannot find coverage file C:\Data\jNetwork\angular-library-cypress\.nyc_output\out.json appears in the console. If you rename the path from angular-library-cypress to angular-library-cy as in the example here, everything works correctly.

You can reproduce the problem with the project https://github.com/philippjenni/angular-library-cypress. Check out the project in the angular-library-cypress folder and execute npm run cypress-project-run. Code coverage will not work. Check out the same project in a folder without the word cypress and execute npm run cypress-project-run. The coverage report is written correctly.

Link to the repo

https://github.com/philippjenni/angular-library-cypress

Lingua principale
TypeScript
Stelle
440
Fork
114
Merge medio
42m
PR unite (30g)
19

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

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

Tutte le issue di cypress-io/code-coverage

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.