-
Notifications
You must be signed in to change notification settings - Fork 17
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
Unit test state #3
Comments
Indeed they haven't =) Thanks for reporting the issue |
I fixed all the ones on the master branch in my local development branch. I can push that one later and create a pull request. I marked all the changes in values with "TODO" so they should be quite obvious. |
Unit test works now, but I will keep this open and make some more tests. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am currently looking at the unit tests and quite a lot of them fail on my platform and there could be several reasons for that.
There's several things here:
I get a lot of those backslashes in my results. I can compensate in the test result of course, but I was wondering if this is something platform specific since I am running Ubuntu 18.04 and python 2.7.
In both tests
specType
should be2
but is0
. Is the unittest outdated or is there a bug in the code?There is also some of those:
But looking at the code it looks like the test hasn't been updated.
The text was updated successfully, but these errors were encountered: