Mercurial > p > roundup > code
view test/README.txt @ 8440:254f70dfc585
bug, refactor, test: make pragma history_length work interactively
history_length could be set interactively, but it was never used to set
readline/pyreadline3's internal state. Using the pragma setting on the
roundup-admin command line did set readline's state.
Also refactored 2 calls to self.readline.get_current_history_length()
into one call and storing in a variable. Also changed method for
creating history strings for printing.
Tests added for history_length pragma on cli and interactive use.
Added test for exiting roundup-admin with EOF on input.
Added test for 'readline nosuchdirective' error case.
Added test to readline with a command directive to set an internal
variable. This last one has no real test to see if it was successful
because I can't emulate a real keyboard/tty which is needed to test.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sun, 31 Aug 2025 20:59:04 -0400 |
| parents | 132d450bdc00 |
| children |
line wrap: on
line source
Getting started: For running the tests, you want to take a look at the documentation in doc/developer.txt, in particular the section "Testing Notes". For a test setup of the database backends, suitable documentation is found in in doc/postgresql.txt for the Postgres backend, in the section titled "Running the PostgreSQL unit tests". For the MySQL backend the file doc/doc/mysql.txt has the documentation in section "Running the MySQL tests". 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)
