From a500ade891c5f2b3e5f7502b6fb121bc733dd0b5 Mon Sep 17 00:00:00 2001 From: Gary Wilson Jr Date: Sat, 2 Aug 2008 00:40:05 +0000 Subject: [PATCH] Removed two-year-old note about testing framework being under development. git-svn-id: http://code.djangoproject.com/svn/django/trunk@8189 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/testing.txt | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/docs/testing.txt b/docs/testing.txt index b7471f852b..c9b23c2948 100644 --- a/docs/testing.txt +++ b/docs/testing.txt @@ -25,13 +25,6 @@ The best part is, it's really easy. This document is split into two primary sections. First, we explain how to write tests with Django. Then, we explain how to run them. -.. admonition:: Note - - This testing framework is currently under development. It may change - slightly before the next official Django release. - - (That's *no* excuse not to write tests, though!) - Writing tests ============= @@ -815,12 +808,12 @@ In order to provide a reliable URL space for your test, configuration for the duration of the execution of a test suite. If your ``TestCase`` instance defines an ``urls`` attribute, the ``TestCase`` will use the value of that attribute as the ``ROOT_URLCONF`` -for the duration of that test. +for the duration of that test. For example:: from django.test import TestCase - + class TestMyViews(TestCase): urls = 'myapp.test_urls'