-
Notifications
You must be signed in to change notification settings - Fork 5
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
new test failures #8
Comments
Hi, I was the one that made the changes to the test suite in that last PR that got merged. Previously there was only one tests that checked all the test cases, meaning that the test run failed as soon as the first assertion failed and leave the rest untested. The new code runs all the tests separately, meaning that all tests cases get executed and you can see all the tests failures. Unfortunately, this code is only better at telling you whats wrong. There were a few PRs (#2 and #1) that were meant to allow for additional postcodes to be valid and that is when this tests started failing. Postcode w1m 4zz and w1m (for non-strict validation) are parsed as valid postcodes when previously they were not. I presume that this test cases are no longer valid and that w1m 4zz and w1m should be valid, but I do not know enough about the postcode rules be able to make a call on this issue. prehaps @simonhayward, @enagorny or @brunns are able to shed some light on this.... |
I just ran into this as well. |
in the version just released to PyPI, I'm getting the following test failures:
Am I doing something wrong?
The text was updated successfully, but these errors were encountered: