out.json file generated without code informations
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
- 25/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Stack tecnológico
- angular, cypress, node.js, typescript
- Área
- testing-qa
Línea de trabajo
Comienza con cypress/support/index.js, cypress/plugins/index.js, .babelrc, cypress.json y los scripts de package.json y la configuración de nyc. Reproduce la advertencia de Cypress e inspecciona si window.coverage está presente y si .nyc_output/out.json recibe mappings y contadores. Se considera completado cuando los datos de cobertura generados contienen información del código en lugar de mapas vacíos.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Logs and screenshots
code-coverage coverage has 0 record(s) +0ms
coverage has the following first paths
code-coverage adding empty coverage for file /home/user/dev/workspace/project/src/main.ts +1ms
code-coverage adding empty coverage for file /home/user/dev/workspace/project/src/polyfills.ts +0ms
code-coverage adding empty coverage for file /home/user/dev/workspace/project/src/test.ts +0ms
code-coverage adding empty coverage for file /home/user/dev/workspace/project/src/app/app-routing.module.ts +0ms
code-coverage adding empty coverage for file /home/user/dev/workspace/project/src/app/app.component.ts +0ms
code-coverage adding empty coverage for file /home/user/dev/workspace/project/src/app/app.module.ts +0ms
...
code-coverage includeAllFiles saving updated file /home/user/dev/workspace/project/.nyc_output/out.json +0ms
code-coverage there are 113 keys in the file +0ms
code-coverage calling NYC reporter with options { 'report-dir': '/home/user/dev/workspace/project/cypress-coverage', reporter: [ 'json', 'lcov' ], extension: [ '.js', '.jsx', '.ts', '.tsx' ], excludeAfterRemap: false, extends: '@istanbuljs/nyc-config-typescript', include: [ 'src/**/*.ts' ], exclude: [ '**/*.d.ts', 'coverage/**', 'packages/*/test/**', 'test/**', 'test{,-*}.ts', '**/*{.,-}{test,spec}.ts', '**/__tests__/**', '**/node_modules/**', 'support-utils.js', 'task-utils.js' ], all: true, 'check-coverage': true, 'temp-directory': '.nyc_output', sourceMap: true, instrument: true, 'temp-dir': '/home/user/dev/workspace/project/.nyc_output', tempDir: '/home/user/dev/workspace/project/.nyc_output', reportDir: '/home/user/dev/workspace/project/cypress-coverage' } +20ms
code-coverage current working directory is /home/user/dev/workspace/project +0ms
Versions
Ubuntu 18.04.5 LTS
Node 14.15.4
NPM: 7.20.5
Angular: 12.0.1
eslint: 7.26.0
My package.json:
"scripts": {
...
"instrument": "npx nyc instrument --compact=false src",
"cypress:open": "ng serve cypress open",
...
},
"devDependencies": {
...
"@babel/core": "^7.14.3",
"@cypress/code-coverage": "^3.9.10",
"@istanbuljs/nyc-config-typescript": "^1.0.1",
"babel-plugin-istanbul": "^6.0.0",
"cypress": "^7.7.0",
"cypress-sonarqube-reporter": "^1.7.1",
"nyc": "^15.1.0",
...
},
,
"nyc": {
"extension": [
".js",
".jsx",
".ts",
".tsx"
],
"extends": "@istanbuljs/nyc-config-typescript",
"include": [
"src/**/*.ts"
],
"exclude": [
"**/*.d.ts",
"coverage/**",
"packages/*/test/**",
"test/**",
"test{,-*}.ts",
"**/*{.,-}{test,spec}.ts",
"**/__tests__/**",
"**/node_modules/**",
"support-utils.js",
"task-utils.js"
],
"all": true,
"check-coverage": true,
"temp-directory": ".nyc_output",
"sourceMap": true,
"instrument": true,
"report-dir": "cypress-coverage",
"reporter": [
"json",
"lcov"
]
}
No, I couldn't see the window.__coverage__ object in the console, as you can see in the printscreen: https://pasteboard.co/5bqIcB10m5xC.png
All the files in out.json file are like this:
"/home/user/dev/workspace/project/src/main.ts": {
"path": "/home/user/dev/workspace/project/src/main.ts",
"statementMap": {},
"fnMap": {},
"branchMap": {},
"s": {},
"f": {},
"b": {}
},
I'm executing Cypress localy.
Describe the bug
Cypress shows the message:
⚠️ Could not find any coverage information in your application
by looking at the window coverage object.
Did you forget to instrument your application?
See [code-coverage#instrument-your-application](https://github.com/cypress-io/code-coverage#instrument-your-application)
`[@cypress/code-coverage]`
I followed all the steps of configuration in the site above. I searched for people that had similar issue, tried all sugestions, but I didn't have success. The report is generated normally.
Here is my configuration:
cypress/support/index.js:
import '@cypress/code-coverage/support';
cypress/plugins/index.js:
module.exports = (on, config) => {
require('@cypress/code-coverage/task')(on, config);
return config;
};
.babelrc:
{
"plugins": ["istanbul"]
}
eslintrc.json:
....
"extends": [..., "next/babel"]
cypress.json:
{
"integrationFolder": "cypress/integration",
"supportFile": "cypress/support/index.js",
"videosFolder": "cypress/videos",
"screenshotsFolder": "cypress/screenshots",
"pluginsFile": "cypress/plugins/index.js",
"fixturesFolder": "cypress/fixtures",
"baseUrl": "http://localhost:4200",
"projectId": "XXXXX",
"reporter": "cypress-sonarqube-reporter",
"env": {
"BABEL_ENV": "e2e"
},
"chromeWebSecurity": false,
"reporterOptions": {
"outputDir": "./sonar",
"overwrite": true
}
}
- 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
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de cypress-io/code-coverage
-
Dificultad 3/5 Medio día Aptitud para principiantes 40/100
cypress-io/code-coverage#1018 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
cypress-io/code-coverage#993 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
cypress-io/code-coverage#967 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
cypress-io/code-coverage#959 ·
Los mantenedores suelen responder en 1 día
-
performance
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
cypress-io/code-coverage#933 ·
Los mantenedores suelen responder en 1 día
Todos los issues de cypress-io/code-coverage
Issues similares
-
area: infrastructure bug priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
snapotter-hq/SnapOtter#4575 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
documentation server-memory v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
modelcontextprotocol/servers#5457 ·
Los mantenedores suelen responder en 1 día
-
comp: ssr comp: zones type: feature version: current (v17+)
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
angular/angularfire#3836 ·
Los mantenedores suelen responder en 3 días
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día