> > We have no "pre-release final check/test". We run the whole test-suite > twice daily. This is done automatically be jenkins. > We try to automate as much as possible. Manual examination is possible, > but who wants to do this? I would like to have it automated. > All tests run in around 10 minutes. >
Hence the reason I mentioned that it will be dependent on your workflow. If this is something you want to automate, obviously you'll need to figure out how to get it to work with your CI implementation. > > I guess we will see bugs like four times per year. > With "like this" I mean: > > * bugs caused by the template engine returning the empy string instead of > an exception > * bugs which are not detected by CI and get into production > I did a bit of poking around and I found this: https://docs.djangoproject.com/en/dev/topics/testing/tools/#overriding-settings It actually looks like it wouldn't be too difficult to take specific existing tests and re-run them in the same test run with the string_if_invalid tweaked. That would save you from having to modify your CI, and would provide coverage in both a 'production mirror' state and the alternative 'template bug catcher' state. You can probably subclass your existing test classes and just decorate them appropriately, although you might have other things you're looking for in those cases. Never tried it myself, but looks to be worth a shot in your case. -James -- 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 django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2Be%2BciWQPAgUMK%3DrvBAHbzwCXvYGfVGZe3n25mcCQOpdxnbVSA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
