RETIRED, further work has moved to Debian project infrastructure
Go to file
2014-09-14 11:51:04 -04:00
alembic fixes for the nose runner 2014-09-14 11:51:04 -04:00
docs/build - move pretty much all of sqlalchemy.testing over for now, as we'd 2014-09-14 11:37:50 -04:00
tests - move pretty much all of sqlalchemy.testing over for now, as we'd 2014-09-14 11:37:50 -04:00
.gitignore - move towards sqlalchemy test base. autogenerate tests so far 2014-09-13 15:38:53 -04:00
CHANGES move the changelog to the new changelog extension 2012-10-20 21:13:47 -04:00
LICENSE - 0.6.3 2014-02-02 19:52:04 -05:00
MANIFEST.in more manifest 2012-01-08 13:43:38 -05:00
README.rst Fix a typo in the README. 2012-10-29 12:32:37 -04:00
README.unittests.rst - add a tox.ini file 2014-09-09 12:10:10 -04:00
run_tests.py - move pretty much all of sqlalchemy.testing over for now, as we'd 2014-09-14 11:37:50 -04:00
setup.cfg - move pretty much all of sqlalchemy.testing over for now, as we'd 2014-09-14 11:37:50 -04:00
setup.py fixes for the nose runner 2014-09-14 11:51:04 -04:00
tox.ini - move pretty much all of sqlalchemy.testing over for now, as we'd 2014-09-14 11:37:50 -04:00

Running Unit Tests

Tests can be run be run using via py.test, nose, or the Python setup.py script:

py.test

nosetests -v

python setup.py test

There's also a tox.ini file with several configurations:

tox

Setting up Optional Databases

The test suite will attempt to run a subset of tests against various database backends, including Postgresql and MySQL. It uses the database URLs in the file test.cfg to locate a URL for particular backend types. If the URL cannot be loaded, either because the requisite DBAPI is not present, or if the target database is found to be not accessible, the test is skipped.

To run tests for these backends, replace URLs with working ones inside the test.cfg file. Setting a URL here requires that the corresponding DBAPI is installed as well as that the target database is running. A connection to the database should provide access to a blank schema, where tables will be created and dropped. It is critical that this schema have no tables in it already.

For Postgresql, it is also necessary that the target database contain a user-accessible schema called "test_schema".