Take a look at Django test utils(formerly test maker) (http:// github.com/ericholscher/django-test-utils/tree/master ), this features some of what you're talking about, helping generate test cases for the user. Ultimately it comes down to the developer knowing more about their application than Django can. You don't want Django generating useless test cases for you just to have tests, you want to test things that might reasonably break, and Django can't just guess at what those would be. If you know of any good strategies for good test generation though a) feel free to let us know, and b) talk to Eric Holscher(the author of django-test-utils), just about anything can be done outside of Django itself so you can always start by implementing it there.
Alex On Jan 5, 6:38 am, HB <hubaghd...@gmail.com> wrote: > I'm a Java guy playing around Django so what I will say may not be > valid. > When I say "encourage testing" I mean generating tests cases whenever > we create a Django entity (like model for example). > Creating integration testing (like Seam application tests). > Include code coverage tool. > Include code complexity tool. > Supports profiles (dev, test, prod) > I will post other thought as I get them :) > > On Jan 5, 2:22 pm, "Russell Keith-Magee" <freakboy3...@gmail.com> > wrote: > > > On Mon, Jan 5, 2009 at 9:04 PM, HB <hubaghd...@gmail.com> wrote: > > > > Sure, I mean encourage not force :) > > > Ok, then - what could we do to encourage testing? > > > We have a test framework; it is documented, there are plenty of blog > > entries around that discuss how to use it, and there are some > > utilities in the community (such as testmaker) that can be used to > > assist. However, if there is something else we could be doing to > > encourage more people to use the test framework, I'm all for it. > > > I have two ideas that I've been intending to work on since I had some > > discussions at DjangoCon. In the interests of full disclosure, I've > > just opened tickets describing them; time permitting, they will be in > > place before v1.1. > > > 1) #9963: Include a dummy test as part of the empty stub application > > that is produced by manage.py startapp. This is a fairly simple > > addition, but well worth it IMHO. > > > 2) #9962: Write a official tutorial on testing. This one is a little > > more effort. If someone wants to volunteer a draft before I get around > > to writing one myself, I'm happy to proofread any offerings as > > candidates for trunk. > > > Of course, any other suggestions are more than welcome. > > > Yours, > > Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
