-
Notifications
You must be signed in to change notification settings - Fork 11
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
Make unit tests #205
Labels
Comments
balintlaczko
added a commit
that referenced
this issue
Sep 29, 2021
balintlaczko
added a commit
that referenced
this issue
Sep 29, 2021
balintlaczko
added a commit
that referenced
this issue
Sep 29, 2021
balintlaczko
added a commit
that referenced
this issue
Sep 30, 2021
balintlaczko
added a commit
that referenced
this issue
Sep 30, 2021
balintlaczko
added a commit
that referenced
this issue
Oct 1, 2021
total test coverage is now 22% #205
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a long-term goal, in order to keep the growing package smooth and bug-free. Currently we mostly test by running the (by now, quite long) jupyper notebook, which is better than nothing, but as the last few issues have shown, there can be bugs which only happen outside the notebook event loop/environment, which will get completely missed by this method. Ideally, we need to create unit tests that test both inside and outside a notebook-like event loop, and can be scheduled to run after every single new commit. It will take some time to write this library of tests, but we have to start somewhere... :)
The text was updated successfully, but these errors were encountered: