Closed dbrgn closed 10 years ago
Please review, @d22
Nice test! Good to merge! Similar changes could/should be made in any view. Should we create an issue for this, or file it under 'General Code Health'.
(I guess the test file is called test_policy.py
because of the app name, right? The name is a little confusing at the moment as no policies are tested there...)
Nice test! Good to merge! Similar changes could/should be made in any view. Should we create an issue for this, or file it under 'General Code Health'.
Could be done in combination with the class based views. Or with code health. The tests would also help us greatly when refactoring the views.
Regarding the test itself, I wonder whether we should change the parametrization to a regular test with a loop, as a failure in one of the values results in many other failures (the tests are not independent).
(I guess the test file is called test_policy.py because of the app name, right? The name is a little confusing at the moment as no policies are tested there...)
Yep.
Regarding the test itself, I wonder whether we should change the parametrization to a regular test with a loop, as a failure in one of the values results in many other failures (the tests are not independent).
I'm not sure if I understand you correctly. With parametrize we have independet tests, I'd say this is what we want, or isn't it?
I'd say merge as it is now!
Only if the tests are independent. See new commit, I think this is better.
:+1: Good to merge!
Found this when grepping for TODOs in the sourcecode.
This raises coverage to 60%.