Timeline for JEST Skipping Tests when Coverage Option Used
Current License: CC BY-SA 4.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 27, 2021 at 13:19 | vote | accept | Dave C | ||
| Aug 27, 2021 at 13:19 | answer | added | Dave C | timeline score: 0 | |
| S Aug 26, 2021 at 18:01 | history | bounty ended | CommunityBot | ||
| S Aug 26, 2021 at 18:01 | history | notice removed | CommunityBot | ||
| Aug 20, 2021 at 19:50 | history | edited | Dave C | CC BY-SA 4.0 |
added 200 characters in body
|
| Aug 20, 2021 at 19:49 | comment | added | Dave C | Thanks for your help, Kris. Added jest.config.js to the post. Nothing I can see there.... | |
| Aug 20, 2021 at 16:20 | comment | added | Kris Goncalves |
If you check your jest.config.js and look at coveragePathIgnorePatterns does it include anything that might match those that are missing?
|
|
| Aug 19, 2021 at 13:43 | comment | added | Dave C | I am also noticing that it executes all the tests too quickly -- it appears to be marking tests as successful without running them. It used to take much longer to run npm run test:unit:coverage when all the tests where correctly displayed in the coverage table. | |
| Aug 19, 2021 at 12:45 | comment | added | Dave C | "jest": "^27.0.6", | |
| Aug 19, 2021 at 12:44 | comment | added | Dave C | sfdx-cli/7.113.0 win32-x64 node-v14.17.4 | |
| Aug 18, 2021 at 18:19 | comment | added | Kris Goncalves | what version of lwc-jest and sfdx cli are you using? | |
| Aug 18, 2021 at 18:00 | history | tweeted | twitter.com/StackSalesforce/status/1428054155298488324 | ||
| S Aug 18, 2021 at 16:35 | history | bounty started | Dave C | ||
| S Aug 18, 2021 at 16:35 | history | notice added | Dave C | Authoritative reference needed | |
| Aug 16, 2021 at 16:10 | history | asked | Dave C | CC BY-SA 4.0 |