-
Notifications
You must be signed in to change notification settings - Fork 7
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
Adding test-case for the data.py #40
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.
This looks good to me!
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.
Thanks for taking the time to build out part of the test suite in an effort to increase test coverage! Much appreciated!
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.
This looks great thank you for putting in the work!
When creating a pull request to add a new feature or alter an existing one,
there are some important elements to include to help our team review and process it more efficiently.
Make sure the title is descriptive of what the PR includes. Don't mention issue names/numbers; save that for the description.
List the names of those who contributed to the project.
Keven Duverglas
Link the issue the pull request is meant to fix/resolve.
Write Tests for All Existing Features #12
Add all labels that apply. (e.g. documentation, ready-for-review)
Did it
Describe the contents and goal of the pull request.
To improve test coverage and to test the features of data.py
Will coverge be maintained/increased?
I believe the test coverage will be increased.
What operating systems has this been tested on? How were these tests conducted?
Unbuntu, these tests were conducted using pytest
Include a code block and/or screenshots displaying the functionality of your feature, if applicable/possible.
Mark as a draft until it is ready to begin the reviewing process, then tag our Lead Software Architect,
Jeff Normile, our Founding Engineer, Gregory Kapfhammer,
and our Project Managers, Haylee Pierce and Sabrina Rodriguez
when you mark it as ready for review.