Hi Jordi, thanks a lot for your response!
Yeah definetly, BUT this error message could change during development and I guess that is the reason why the django-docs recon you to set error_codes. This why you wouldn't have to touch the tests when changing the error-message but keeping the error-code the same. Any other ideas? *Does anyone know how to raise an error_code-exception within the model and keep the view rendering the invalid-fields correctly?* Am Montag, 3. August 2015 00:34:18 UTC+2 schrieb jordi collell: > > An easy way is to test that the rendered form has the error message raised > suring rhe validation. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/cf2ab717-faff-4ea8-a46a-6580745e790a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
