Changes between Version 3 and Version 4 of TestingDjango


Ignore:
Timestamp:
09/15/2007 06:54:54 AM (8 years ago)
Author:
Simon G. <dev@…>
Comment:

adding in-memory settings.py and fixing a few typos.

Legend:

Unmodified
Added
Removed
Modified
  • TestingDjango

    v3 v4  
    2929
    3030{{{
     31# settings_memory.py
     32# this should be faster than the others because it uses an in-memory SQLite
     33DATABASE_ENGINE = 'sqlite3'
     34DATABASE_NAME = ':memory:'
     35DATABASE_USER = ''       
     36DATABASE_PASSWORD = ''   
     37DATABASE_HOST = ''       
     38DATABASE_PORT = ''       
     39
     40LANGUAGE_CODE = 'en-us'
     41SITE_ID = 1
     42ROOT_URLCONF = ''
     43}}}
     44
     45
     46{{{
    3147# runtests.sh
    32 # runs the django tests, loggs the output
     48# runs the django tests, logs the output
    3349
    3450set -x
     
    4864}}}
    4965
    50 note: most of the runtests.py output is to stderr.  the 2>&1 redirectes that to sdtout so that it can be redirected into a file, which is handy for posting when tests fail.
     66Note: most of the runtests.py output is to stderr.  the 2>&1 redirects that to stdout so that it can be redirected into a file, which is handy for posting when tests fail.
    5167
    5268See also #4223
    5369
     70== Test Locations ==
     71
    5472If you write tests place them as follows:
    5573
    56  * if the test tests a core feature of models, it should live in modeltests;
    57  * if it tests a contrib app it should live as a test module in the contrib app itself;
    58  * otherwise it should go in regressiontests
     74 * if the test tests a core feature of models, it should live in ''modeltests'';
     75 * if it tests a ''contrib'' app, it should live as a test module in the ''contrib'' app itself;
     76 * otherwise it should go in ''regressiontests''
Back to Top