Before this thread goes too far, I'd like to express my doubts regarding the goals you stated.
2014-02-27 20:50 GMT+01:00 Akshay Jaggi <[email protected]>: > > *Need for Improvement/ Current Problems* > > 1. Running of Test Cases is slow. > > I don't know what the threshold for "slow" is, but faster is obviously better ;-) However, could you clarify how changing the test runner will make the tests run faster? I gained a little bit of experience in that area when I helped divide by three the run time of the test suite last year. I don't believe unittest even registers on the radar of things that make the tests slow. If you haven't heard the "Database is Hot Lava" meme, google it. > > 1. Selection of what tests we want to run, and what all we don't want > to run is difficult > > That problem can be solved by a custom test runner extending unittest, without changing -- and maybe breaking -- the semantics of the tests. I've been working on this codebase for some time and I have a hard time to believe someone will actually audit all of the 5000 test cases. Some are really tricky -- like, with threads, database transactions, hacks for in-memory SQLite, and some selenium. > > 1. We have better options available > > It's hard to take such a blanket statement at face value. You need to argue why py.test is better *for Django*. For starters, using standard tools from the standard library helps lowering the barrier to contributing. Every change must come with a test, and if that involves learning a new test runner and a complex categorisation system, that's an additional barrier. Don't get me wrong -- I know that py.test is a good tool. I'm just saying that you shouldn't start rewriting chunks of Django's test suite without convincing the core team that you understand the problem you're trying to solve. -- Aymeric. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CANE-7mWBMHmj3nCwbid0eusDDte52jfEa2ab-_1nxQjV74_HVQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
