> On Sat, 2011-03-12 at 00:12 -0800, Mike Ramirez wrote:I've een wondering about this myself, but I'm not sure that it's in the wrong
> > On Friday, March 11, 2011 11:37:38 pm Kenneth Gonsalves wrote:
> > > and all is well. I think the dev docs need to be clearer on this
> > point
> > > and mention this at the outset. After all they *are* dev docs.
> I know it is there - but it is half way down the page. My point is that
place, but it's not in the perfect place.
IMO, it's in its natural place if you apply how the other docs are split up.
If you look at the forms api, it describes the basic forms api with just
Testing works the same way, introducing the basic unit testing functionality,
Also starting with unittest shows that we can use unittest as we need (in a
ftr, in atleast 1.2.3 forward startapp generates a tests.py with this code:
[gmike@priss keis]$ cat newfun/tests.py
Replace this with more appropriate tests for your application.
from django.test import TestCase
*note: 1.2.3 also has docstring tests included as part of the sample/exmaple.
With this all in mind, I think they do enough to say use 'django.testing',
But it could possibly benefit from being two pages, one an "overview" and one
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.