Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coverage fail for exported object modules with babel-jest #8637

Closed
klarkc opened this issue Jul 3, 2019 · 3 comments · May be fixed by joseroubert08/jest#34 or joseroubert08/jest#76
Closed

Coverage fail for exported object modules with babel-jest #8637

klarkc opened this issue Jul 3, 2019 · 3 comments · May be fixed by joseroubert08/jest#34 or joseroubert08/jest#76

Comments

@klarkc
Copy link

klarkc commented Jul 3, 2019

🐛 Bug Report

ES Modules that are objects (not functions) are bypassed/ignored by coverage tests, even with written tests for the module.

Confirmed in following versions: 24.6, 24.7.*, 24.8 (23.6 is working normally)

To Reproduce

  • Install dependencies
  • Execute coverage tests with npx jest

Expected behavior

All js files being covered (green), no coverage errors

Link to repl or repo (highly encouraged)

https://github.com/klarkc/jest_cov_bug/

Run npx envinfo --preset jest

  System:
    OS: Linux 4.15 Ubuntu 18.04.2 LTS (Bionic Beaver)
    CPU: (4) x64 Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz
  Binaries:
    Node: 12.4.0 - /usr/local/bin/node
    Yarn: 1.16.0 - ~/.npm-global/bin/yarn
    npm: 6.9.0 - ~/.npm-global/bin/npm
  npmPackages:
    jest: ^24.8.0 => 24.8.0 
@github-actions
Copy link

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the Stale label Feb 17, 2023
@github-actions
Copy link

This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 19, 2023
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants