Add more explicit steps to the Getting Started example #114
Labels
documentation
Improvements or additions to documentation
good first issue
Good for newcomers
sprint-friendly
A good issue for sprint events
Improve the Getting Started section of the docs.
Right now it's easy to miss that two files are needed: a notebook (
.ipynb
file) to test and a test file (.py
file) to write the tests.It would also be helpful to add an explicit step on how to run the test file.
The text was updated successfully, but these errors were encountered: