-
Notifications
You must be signed in to change notification settings - Fork 8
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
Improvement pytest #7
Conversation
…on-generic into improvement-pytest
…:cisagov/skeleton-generic into improvement-pytest
So this PR adds unit tests, and code coverage checks. I think we should start maturing our test writing chops sooner than later. As the team grows the tests will give new members some confidence that they aren't committing system breaking changes. Also, chasing a 100% code-coverage can be a new pastime. A bigger change is that I moved Let me know what you think. |
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 think these changes are good, but please see my comment. Ideally we could find a solution that lets us run bandit
with the assert check enabled on the library code and disabled on the unit test code.
I wholeheartedly agree that we need to get into the test writing business. 👍
One for tests and one for everthing else.
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 solution!
No description provided.