Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
feat: add codecov to the project #3168
feat: add codecov to the project #3168
Changes from all commits
ec09642
566c37b
a8814ec
0a997a3
cef181b
6d4d293
fd92de6
7e2c409
2791cfd
6a1f40f
451acf3
347d752
859e9dc
4ce435f
f29052d
af14485
354871b
ca47e34
75d4483
9cc0dc1
af99e29
e20d236
fd57791
829c653
0bde97f
d3541cb
efe6ab9
16f4651
37bea64
4a15cee
1643499
8f79d8a
3fe50cd
6dab16d
d745bb1
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did you remove this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't need that jest will only include files that are directly imported in our test files for coverage.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's the case. Jest is now taking
fixture
files also into coverage, and that's wrong.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will update it for excluding fixture files
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codebase verification
Coverage reports are not being generated.
Despite
collectCoverage
being enabled injest.config.js
, thecoverage
directory does not exist. This indicates that coverage reports are not being generated as expected.Please ensure that:
🔗 Analysis chain
Verify coverage collection configuration.
The current
collectCoverageFrom
configuration includes only 'scripts/**/*.js'. Based on the previous discussion in the comments, there was a concern about including 'fixture' files in the coverage reports.Please verify if the current configuration sufficiently excludes 'fixture' files from coverage reports. If not, consider updating it to explicitly exclude these files.
To check if 'fixture' files are being included in coverage reports, you can run the following command after running your tests:
If 'fixture' files are found in the coverage report and you want to exclude them, you might want to update the
collectCoverageFrom
configuration to something like:This will include all .js files in the 'scripts' directory and its subdirectories, but exclude any files in 'fixtures' directories.
Length of output: 92
Script:
Length of output: 100
Script:
Length of output: 157
Script:
Length of output: 85
Script:
Length of output: 72
Script:
Length of output: 430
Script:
Length of output: 248
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
coverage directory has been added in the .gitignore, hence it won't be part of repo. The coverage is generated everytime during github action run.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akshatnema, thank you for the clarification. I understand that the
coverage
directory is gitignored and coverage reports are generated during the GitHub Actions run. That makes sense.(_/)
(o.O)
✏️ Learnings added