Skip to content

Conversation

MikeMeliz
Copy link
Owner

Description

Implement unit tests to start building a good habit of having coverage for feature additions.

Motivation and Context

Coverage will make sure that any commit/PRs from now on will not break future versions, and ensure that future users will have the best experience.
Related issue here: #16

How Has This Been Tested?

Local tests and reporting. But overall, the reporting will happen in SonarQube Cloud.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • N/A

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

@MikeMeliz MikeMeliz self-assigned this Jun 28, 2025
@MikeMeliz MikeMeliz linked an issue Jun 28, 2025 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implementation of Unit Tests
1 participant