question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Coverage report not generated

See original GitHub issue

I’m testing Peeky and I setup it to generate the coverage report as described in the docs [https://peeky.dev/guide/config.html#coverageoptions] but the folder isn’t created nor the files

This is how I have it on my vite.config file

export default defineConfig(({ mode }) => {
    process.env = {
        ...process.env,
        ...loadEnv(mode, process.cwd()),
    };
    const brand = process.env.VITE_APP_BRAND;

    return {
        test: {
            // Peeky options here...
            runtimeEnv: 'dom',
            collectCoverage: true,
        },
        coverageOptions: {
            reportsDirectory: './coverage',
            excludeNodeModules: true,
            exclude: [
              'coverage/**',
            ],
            reporter: ['text', 'html'],
            extension: ['.js', '.cjs', '.mjs', '.ts', '.tsx', '.jsx', '.vue'],
        },
        ...
   };
});

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
Akryumcommented, Feb 22, 2022

Looks like you are using an older version of peeky.

0reactions
victorlmnevescommented, Feb 23, 2022

@Akryum I already knew about that issue, but I believe you were using a different tool before as I went to check the changes, and C8 was added now. But yeah, looks like I need to wait for them to fix it as I don’t have the knowledge to do it. I just mention it because I did a POC with Peeky and Vitest to choose one to add to the project that we are starting and the team has pointed it as an extra point compared to Vitest to have on the report, Vue files that didn’t have a test. Thanks

Read more comments on GitHub >

github_iconTop Results From Across the Web

maven jacoco: not generating code coverage report
In your configuration, the report goal is bound to the verify phase, so running mvn test won't generate any report because it does...
Read more >
No coverage report generated for large project #434 - GitHub
When running tests on PROJECT-1, I get consistent coverage reports. I never see coverage reports for PROJECT-2.
Read more >
Coverage reports is not generating after sonar scan analysis
We do generate some reported coverage with our sonar scan report. The reason we are concerned is because our line coverage reported by...
Read more >
How To Generate Code Coverage Report Using JaCoCo ...
In this tutorial, you will learn about generating code coverage reports using the JaCoCo-Maven plugin.
Read more >
Munit Coverage reports not being generated as expected ...
When running Munit tests from the command line you are not seeing coverage reports generated either in the console or in HTML /...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found