Hi Russ, On 05/09/2013 04:51 AM, Russell Keith-Magee wrote: > Great work Carl and Preston! (And everyone else who had a hand in the > patch - I know this has been kicking around for a while now)
Thanks for the reminder; I should have mentioned that Mahdi Yusuf did the initial draft patch, based on Jannis' django-discover-runner, which was based on code I showed on a slide in my "Django and Testing" talk at PyCon 2012; it all comes full circle :-) > I agree with Jacob's tests aren't production sensitive, so making a fast > transition to the new test discovery has less impact. > > However, we know from experience that it doesn't matter how much we flag > this change in the release notes, they won't be read, and *someone* is > going to get stung. In an ideal world, it would be good to be able to > warn people who upgrade that their test suite may not be run as expected. > > We've had a proposal kicking around for a while to add a management > command that does an "upgrade check". I'm wondering if this might be an > opportune time to dig into this some more. > > To be clear, this isn't something I consider to be a merge blocker. I'd > be happy to see 1.6 released with a fast transition to the new test > runner. It would just be nice icing on the cake if we can get an upgrade > validator included in the same release. It wouldn't be too hard to write something that tried test discovery using the old runner and using the new runner and did a simple comparison of test counts to warn you if they differ. I'm not personally likely to work on this "upgrade checks" framework, but if it does happen I'd be happy to contribute this check to it. Carl -- You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
