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

fix: running tests and adding tests to CI & CD #1047

Merged
merged 4 commits into from
May 24, 2022
Merged

Conversation

karolsojko
Copy link
Member

No description provided.

Comment on lines 28 to 35
coverageThreshold: {
global: {
branches: 3,
functions: 5,
lines: 21,
statements: 23,
},
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The positive numbers in "coverageThreshold" mean percentage, so maybe it makes more sense to increase these numbers (like to have branches coverage e.g. 60% instead of 3%)? Or the numbers are small in order to have the existing tests with low coverage passing right now?
https://jestjs.io/docs/configuration#coveragethreshold-object

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, the intention here is to define the threshold in a way that does not allow it to get any lower. So this is the "current state" of coverage and we don't want it to get worse :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants