Code-Coverage plugin does not work reliably when run in an Azure Pipeline

Offen
  • Stimmt etwas nicht?
#656 2 Kommentare 0 Reaktionen 2 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@marktnoonan arbeitet bereits daran.

Seit 27.6.2023.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

Logs and screenshots

Cannot find coverage file C:\azure_devops_agent\_work\8\s\packages\cypress-honeybee-e2e\.nyc_output\out.json
Skipping coverage report

Versions

  • What is this plugin's version?
    • "@cypress/code-coverage": "^3.10.4"
  • What is Cypress version?
    • "cypress": "^12.5.0"
  • What is your operating system?
    • Tried on Windows 10 and Ubuntu Linux (20.04), both OSs show the same behavior
  • What is the shell?
    • Windows: tried with CMD and Powershell Core
    • Linux: tried with BASH and Powershell Core
  • What is the Node version?
    • node 18.15.0
  • What is the NPM version?
    • npm 8.19.3
  • How do you instrument your application?
    • The MFEs are instrumented with Babel and the Instanbul plugin
  • 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?
    • I had to blur the picture due to confidential information in it but I hope you get the impression of the window.__coverage__ object
    • image
  • 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?
    • Here is the basic problem. Please see the bug description below.
  • Do you have any custom NYC settings in package.json (nyc object) or in other NYC config files
    • package.json:
    "nyc": {
        "extends": "@istanbuljs/nyc-config-typescript",
        "all": true,
        "exclude": [ /* a list of glob patterns */ ] 
     }
  • Do you run Cypress tests in a Docker container?
    • No

Describe the bug
If we ran the pipeline e.g. three times consecutively, there is the possibility to have two times a .nyc_output folder and an out.json file with data in it and one time we will have an unsuccessful attempt (with the error message above). But there is also the possibility to have it the other way around (one successful and two unsuccessful), three successful attempts, or no successful attempt at all. No changes are made to the test code or the NYC configuration between the runs.
Additionally, I tried to create a .nyc_output/out.json file with an empty JSON object (e.g. { } before the runs, which lead to another error message and no data in out.json. So I removed this intermediate step again.

Vorherrschende Sprache
TypeScript
Sterne
440
Forks
114
Ø Merge
42 Min.
Gemergte PRs (30 T.)
19

Entwicklungsumgebung

  • Kein Dockerfile und keine Docker-Compose-Datei
  • Hat eine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus cypress-io/code-coverage

Alle Issues in cypress-io/code-coverage

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.