Added coverage per @lathonez #68
Merged
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.
This Pull Request is a replacement for @lathonez's PR #12 for adding Code Coverage for tests. My inability to merge that PR led to my recreating the changes and placing them into a new PR.
All the hard work on this PR was performed by @lathonez. Thanks, Stephen, for the original PR, your leadership, and all the work you are doing with clicker.
With this update, developers can run
npm run test-coveragewhich will run the project's unit tests with Karma and produce documentation that gives guidance on how well the project's tests cover the code.The documentation is created inside the
/coveragefolder (ignored by git).