Parse threshold information from jest configuration in 'package.json'
See original GitHub issueIssue Analytics
- State:
- Created 2 years ago
- Reactions:9
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Configuring Jest
This will be used to configure minimum threshold enforcement for coverage results. Thresholds can be specified as global , as a glob, and...
Read more >Configuring package.json · Jest
This config option lets you customize where Jest stores that cache data on disk.
Read more >Configuring Jest compiled - w3resource
In this tutorial we will focus on configuring Jest. Jest's configuration can be defined inside the package.json file of your project, ...
Read more >How to set coverageThreshold with CLI · Issue #7509 - GitHub
The argument should be a JSON string, but the below command always doesn't work. jest --coverage --coverageThreshold='{\"global\":{\"branches\": ...
Read more >Configuring code coverage in Jest, the right way
coverageThreshold. As a good starting point for any project, here's a minimal package.json configuration on which you can build up (Jest can ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@grahammcculloch,
Sorry, I just now realized how vague this issue is. This issue is not about parsing jest configuration, it is about taking threshold information from the jest configuration, because action should show clear message, when threshold values are not met.
This action don’t use any jest configuration to actually run tests, it simply runs the script, which is specified as
test-script
input (here is the docs link). So if jest not takes information frompackage.json
file, it is most likely that something is wrong with yourtest-script
option.I’m glad this has been suggested as it’s a problem I’m encountering. Specifically, in my case, the config in
package.json
is for a Create React App: