-
Notifications
You must be signed in to change notification settings - Fork 0
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
Configuring Codeclimate And Adding Test coverage #20
Conversation
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.
Great job
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 have seen no errors
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.
No errors seen
…bo-32-bn into ft-codeclimate-test_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.
Some files could not be reviewed due to errors:
Oops! Something went wrong! :( ESLint: 4.19.1. ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons: 1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin. 2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following: npm i eslint-plugin-@typescript-eslint@latest --save-dev If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.
Configuring Codeclimate And Adding Test coverage
Configuring Codeclimate And Adding Test coverage
What does this PR do?
This PR integrates test coverage reporting into the project using CodeClimate and adds a coverage badge to the README file to display the current test coverage status.
Describe your changes
1.Added Coverage Reporting:
Installed the codeclimate-test-reporter package.
Configured Jest to generate lcov coverage reports.
Updated CircleCI configuration to run tests, generate coverage reports, and upload them to CodeClimate.
Configured Coverage Thresholds:
2.Enforced a minimum test coverage threshold in CodeClimate settings.
Added Coverage Badge to README:
3.Included a test coverage badge at the top of the README.md file.
PR Type
What kind of change does this PR introduce?
[ ] Bugfix
[x] Feature
[ ] Refactoring (no functional changes, no api changes)
[x] Documentation content changes
[x] Tests
[ ] Other
How should this be manually tested?
1.Check Test Coverage Reporting:
Push a commit to trigger the CircleCI build.
Verify that tests run and the coverage report is generated and uploaded to CodeClimate.
2.Check Coverage Badge:
Ensure the coverage badge in the README.md file reflects the current test coverage percentage.
What are the relevant pivotal tracker stories?
Pivotal Tracker Link