Mercurial > p > roundup > code
view test/README.txt @ 5111:1c94afabb2cb
Fix mark_class decorator to work in all cases
The 'mark_class' decorator assumed that all test functions started with
'test_' which is the common naming convention these days. The roundup
codebase predates many of the current common conventions though though,
so many tests don't include the underscore. We now correctly check for
any test function starting with 'test' and also ensure the 'mark_class'
will also work with functions as well as classes.
This has been tested will all package dependencies missing, and all the
tests correctly skip. All the tests also pass a full test run without
any tests being skipped. A smattering of other runs of individual test
files and enabled dependencies seem to indicate that all skipping should
work as expected now.
| author | John Kristensen <john@jerrykan.com> |
|---|---|
| date | Thu, 30 Jun 2016 12:38:23 +1000 |
| parents | a86b0c02940d |
| children | 132d450bdc00 |
line wrap: on
line source
A number of tests uses the infrastructure of db_test_base.py grep "from db_test_base" -l *.py benchmark.py session_common.py test_anydbm.py test_indexer.py test_memorydb.py test_mysql.py test_postgresql.py test_security.py test_sqlite.py test_userauditor.py grep "import db_test_base" -l *.py test_cgi.py test_jinja2.py test_mailgw.py test_xmlrpc.py grep "import memory\|from memory" -l *.py test_mailgw.py test_memorydb.py The remaining lines are an 2001 description from Richard, which probably is outdated: Structure of the tests: 1 Test date classes 1.1 Date 1.2 Interval 2 Set up schema 3 Open with specific backend 3.1 anydbm 4 Create database base set (stati, priority, etc) 5 Perform some actions 6 Perform mail import 6.1 text/plain 6.2 multipart/mixed (with one text/plain) 6.3 text/html 6.4 multipart/alternative (with one text/plain) 6.5 multipart/alternative (with no text/plain)
