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
add testing heading to readme #373
Conversation
Codecov Report
@@ Coverage Diff @@
## master #373 +/- ##
=======================================
Coverage 95.85% 95.85%
=======================================
Files 89 89
Lines 7798 7798
=======================================
Hits 7475 7475
Misses 323 323 Continue to review full report at Codecov.
|
README.md
Outdated
@@ -78,6 +78,13 @@ In this demonstration, we use a multi-table dataset of 3 million online grocery | |||
|
|||
For more examples of how to use Featuretools, check out our [demos](https://www.featuretools.com/demos) page. | |||
|
|||
## Testing |
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.
These instructions should get added to the development section in the install page (https://docs.featuretools.com/getting_started/install.html#development).
You can create a development section in the readme and like to that url too.
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.
Ah. I hadn't looked in the docs, and had checked the readme instead. To avoid duplication, would it make sense just to link from the readme to the docs url?
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.
that sounds good to me
Pushed. Python tests will fail likely fail because of the pandas 0.24.0 and linter update, but no code has changed. Should be good to merge. |
Made one change to the capitalization of Featurefools. Otherwise, looks good. Thanks! |
Related to #371