sqlalchemy-timezone / README.unittests


To run unit tests (assuming unix-style commandline, adjust as needed for windows):

Python 2.4 or greater is required since the unit tests use decorators.

cd into the SQLAlchemy distribution directory.

Set up the PYTHONPATH.  In bash:

    export PYTHONPATH=./test/

On windows:

    set PYTHONPATH=test\

The unittest framework will automatically prepend the lib directory to
sys.path.  This forces the local version of SQLAlchemy to be used,
bypassing any setuptools-installed installations (setuptools places
.egg files ahead of plain directories, even if on PYTHONPATH,

To run all tests:

    python test/

Help is available via:

    python test/ --help

    usage: [options] [tests...]
      -h, --help            show this help message and exit
      --dburi=DBURI         database uri (overrides --db)
      --db=DB               prefab database uri (sqlite, sqlite_file, postgres,
                            mysql, oracle, oracle8, mssql)
      --mockpool            use mock pool
      --verbose             enable stdout echoing/printing
      --log-info=LOG_INFO   turn on info logging for <LOG> (multiple OK)
                            turn on debug logging for <LOG> (multiple OK)
      --quiet               suppress unittest output
      --nothreadlocal       dont use thread-local mod
                engine strategy (plain or threadlocal, defaults to SA
      --coverage            Dump a full coverage report after running    

Any unittest module can be run directly from the module file (same commandline options):

    python test/orm/

Additionally, to run a speciic test within the module, specify it as ClassName.methodname:

    python test/orm/ MapperTest.testget

Logging is now available via Python's logging package.  Any area of SQLAlchemy can be logged 
through the unittest interface, such as:

Log mapper configuration, connection pool checkouts, and SQL statement execution:

    python test/orm/ --log-info=sqlalchemy.orm.mapper --log-debug=sqlalchemy.pool --log-info=sqlalchemy.engine

Coverage is now integrated through the module, included in the './test/' directory.  Running the test suite with
the --coverage switch will generate a local file ".coverage" containing coverage details, and a report will be printed
to standard output with an overview of the coverage gathered from the last unittest run (the file is deleted between runs).

After the suite has been run with --coverage, an annotated version of any source file can be generated
marking statements that are executed with > and statements that are missed with !, by running the
utility with the "-a" (annotate) option, such as: 

    python ./test/ -a ./lib/sqlalchemy/

which will create a new annotated file ./lib/sqlalchemy/,cover .  Pretty cool !

When running the tests on postgres, postgres gets slower and slower each time you run the tests.  
This seems to be related to the constant creation/dropping of tables.  Running a "VACUUM FULL" 
on the database will speed it up again.
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.