-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
Missing tests #42
Comments
I can look into this, would be nice to finish these before we release what's on development. |
I agree. I think the most important thing is to see if these errors are compliant with the standard, I think there were issues in the original repo complaining about errors being different from what the standard describes but I am on the run right now so I can't really check |
@jorenvandeweyer made already the first step for real integration tests in his #100 PR Tbh I think we should implement more of those tests. |
I agree! |
Will be covered in V5 release. see #219 |
When running the code coverage there are still a few lines uncovered:
I checked the files and all of them were missing checks for thrown Errors/Exceptions. Since throwing specific errors in specific situations is a crucial part of the standard we should at least check, whether these errors are correct / compliant or not.
The text was updated successfully, but these errors were encountered: