jest
jest copied to clipboard
[Bug]: Incorrect "global" coverageThreshold handle, while nested directories thresholds are defined
Version
29.7.0
Steps to reproduce
- Clone my repo https://github.com/vvscode/jest-coverage-issue-demo
-
npm install
-
npx jest --config jest.config.js
-
npx jest --config jest.configWithCollectCoverageFrom.js
There is unexpected (by me) behaviour (described in README)
Expected behavior
I expected being able to define global threshold as well as nested modules ones
Actual behavior
Global threshold is not handled properly (not counted or counted incorrectly) if nested one is defined
Additional context
No response
Environment
System:
OS: macOS 13.4.1
CPU: (10) arm64 Apple M1 Pro
Binaries:
Node: 20.8.0 - /opt/homebrew/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 10.2.1 - /opt/homebrew/bin/npm
npmPackages:
jest: ^29.7.0 => 29.7.0
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.
@cpojer @SimenB hey =)
not trying to prioritise this minor issue, but I'd like to understand the expected workflow for reporting
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.
is anyone observing the list of issues? =)
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.
sad to see full ignore =(
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.
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.
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.
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.