fixing sonar issue #494
Merged
fixing sonar issue #494
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull Request Description: Fixing Sonar Issue
This pull request addresses several issues identified by SonarQube related to code coverage and reporting. The changes made in this PR enhance the overall quality and maintainability of the project.
Key Changes:
.coveragercfile to include relative paths, ensuring accurate coverage reporting.coverage-badge.svgto reflect the current coverage percentage accurately, which is now at 77.63%. This transparency helps maintain awareness of the project's testing status.coverage.xmlfile has been updated to reflect the accurate line coverage metrics and paths, providing a more accurate representation of the codebase's test coverage.Motivation:
By fixing the Sonar issues, we ensure that the project adheres to best practices in code quality and maintainability. Improved test coverage metrics and accurate reporting allow the team to identify untested areas of the codebase more effectively, leading to higher quality releases and reducing the risk of undetected bugs.
These changes are essential for maintaining a clean codebase and fostering a culture of quality within the team.