I'm not trying to be antagonistic, sorry if I came off that way. I wanted to point out the difficulties that Django encountered trying to provide "integration" tests like django-otp does. As others suggested, if django-otp provided tools to build your own integration tests, that might be a better way forward.
On Wednesday, February 22, 2017 at 10:14:26 AM UTC-5, Tom Evans wrote: > > On Wed, Feb 22, 2017 at 2:40 PM, Tim Graham <timog...@gmail.com > <javascript:>> wrote: > > I'm curious if you feel that running django_otp's tests as part of your > > project's tests is adding value. > > I'm curious whether you think I commonly spend my time doing things > that I don't think add value... > > django_otp is simply an example of this issue, but yes, running those > tests would give my project value. > > These tests exercise parts of django_otp that interact with parts of > my code. Successful tests indicate that those two parts interoperate > correctly. The tests are successful when run individually, but fail > when run as a suite because data loaded as part of a migration is > flushed away before the second test. > -- 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/751918fc-a96f-469b-bd3e-b19a10adf15a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
