Mercurial > p > roundup > code
view test/README.txt @ 5034:4ad465b09cbe
Update test/test_actions.py to work with py.test
The test_actions tests use a FieldStorage object to mock form
submissions. FieldStorage would usually use the 'QUERY_STRING'
environment variable to populate the initial list of MiniFieldStorage
values stored within the FieldStorage object, but because there is no
'QUERY_STRING' environment variable when running the test from the
commandline it tries to parse sys.argv instead. If any py.test options
are used (ie. '--tb=short') then they may end up in the MiniFieldStorage
list causing some tests to fail because they were not expecting the
extra MiniFieldStorage values.
To fix this we explicitly pass an dict with an empty 'QUERY_STRING'
value as the FieldStorage environ argument to ensure that the initial
MiniFieldStorage list is empty.
| author | John Kristensen <john@jerrykan.com> |
|---|---|
| date | Thu, 20 Aug 2015 16:30:50 +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)
