Mercurial > p > roundup > code
view test/README.txt @ 6643:5b71a50e833b
try to get more info on failing test
looks like m is not being formatted for markdown2 test case. No idea
why. Trying to make output more verbose to figure out what's happening.
pip in ci reports version 2.4.2 of markdown2 according to:
https://app.travis-ci.com/github/roundup-tracker/roundup/jobs/568309619
same version I run locally with python 3.6.9. Fails in CI on 3.6, 3.8,
3.10.4.
python 2.7 works on with version 2.3.10 of markdown2
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Thu, 28 Apr 2022 00:19:52 -0400 |
| 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)
