Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Test reordering and TransactionTestCase cleanup

Received: by 10.236.189.9 with SMTP id b9mr5010038yhn.8.1336072656889;
        Thu, 03 May 2012 12:17:36 -0700 (PDT)
X-BeenThere: django-developers@googlegroups.com
Received: by 10.236.114.50 with SMTP id b38ls2462029yhh.1.gmail; Thu, 03 May
 2012 12:17:24 -0700 (PDT)
Received: by 10.236.76.4 with SMTP id a4mr5016485yhe.2.1336072644538;
        Thu, 03 May 2012 12:17:24 -0700 (PDT)
Received: by 10.236.76.4 with SMTP id a4mr5016482yhe.2.1336072644521;
        Thu, 03 May 2012 12:17:24 -0700 (PDT)
Return-Path: <kmtra...@gmail.com>
Received: from mail-gy0-f182.google.com (mail-gh0-f182.google.com [209.85.160.182])
        by gmr-mx.google.com with ESMTPS id t12si3661816yhh.7.2012.05.03.12.17.24
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 03 May 2012 12:17:24 -0700 (PDT)
Received-SPF: pass (google.com: domain of kmtra...@gmail.com designates 209.85.160.182 as permitted sender) client-ip=209.85.160.182;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of kmtra...@gmail.com designates 209.85.160.182 as permitted sender) smtp.mail=kmtra...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-gy0-f182.google.com with SMTP id r20so2743518ghr.13
        for <django-developers@googlegroups.com>; Thu, 03 May 2012 12:17:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=VTL9iSKzDO2qicnmd7AdOSbWkaM1C9pr3r+cLJz0OtQ=;
        b=oEVgWzf+62U8TsEpkHuSXfQTrcPesX6LLRz0BQYHmF7SJtYV6/uaMwk24HwQpBZQKD
         C9FsNuZSarXjxWEP6OTgDrcQQc+YFAcdMh6sshZpZFocIu8Si9mAO6G2vnNKmVH2czTJ
         +zUgMrO6ZRSJNyo+UYHpZaqKkeSFd1WnJ9DIxuTSVcMQEYpRD9JC0HCG8vS2MD+VXHMN
         CArvhdc3/1InlqI6z/MYCM82EYO2I6tAdp2NV/1j69bRMnkt3r/694CwAN3LLF4bqlMQ
         Op4gP2k4zDJeo4/EhT9uOFs3c86z5t0wpAeiD6HEqTtFUnipB1WSyA7q6bgT+rS+CrmM
         Htqw==
MIME-Version: 1.0
Received: by 10.60.18.137 with SMTP id w9mr4584897oed.7.1336072644390; Thu, 03
 May 2012 12:17:24 -0700 (PDT)
Received: by 10.182.32.168 with HTTP; Thu, 3 May 2012 12:17:24 -0700 (PDT)
In-Reply-To: <B86645F52B164CE4AC4C364B1FFA0...@pelme.se>
References: <B86645F52B164CE4AC4C364B1FFA0...@pelme.se>
Date: Thu, 3 May 2012 15:17:24 -0400
Message-ID: <CACS9raeiz2Mkz_02G4S6Qo_itJt2081D_=vDCh-uAEx7TZw...@mail.gmail.com>
Subject: Re: Test reordering and TransactionTestCase cleanup
From: Karen Tracey <kmtra...@gmail.com>
To: django-developers@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1

On Thu, May 3, 2012 at 12:29 PM, Andreas Pelme <andr...@pelme.se> wrote:
>
> Djangos default testrunner reorders the test suite to run all TestCase tests before TransactionTestCases, which avoids this problem. I cannot find this reordering documented anywhere,

It is documented:
https://docs.djangoproject.com/en/1.4/topics/testing/#django.test.TransactionTestCase

Mentioned in both the 3rd paragraph and the note.

Karen