| commit | ee377d54917e99db25075f9944117d308d8fcb58 | [log] [tgz] |
|---|---|---|
| author | Sebb <sebb@apache.org> | Sun Sep 13 12:57:09 2020 +0100 |
| committer | Sebb <sebb@apache.org> | Sun Sep 13 12:57:09 2020 +0100 |
| tree | ba085fb56d4a0ebe19653b59e959536b95256ed7 | |
| parent | 97dd66032f3b0100a1fce75f31dd2a25182010c7 [diff] |
No longer relevant
The aim of this repository is to create a comprehensive suite of tests for ensuring that changes to the Pony Mail codebase does not impact stability and reproducibility.
The repository is split into three main directories:
tests/: The python test scriptsyaml/: The test specificationscorpus/: The test corpus (data input to be used during tests)The root directory has a runall.py, which will run all tests it can find in the yaml directory, and summarize the results at the end. You may also run individual tests from the tests directory (more on that as we build out the test dir).
CLI args for runall.py:
--rootdir: The root filepath of your Apache Pony Mail installation to test against--fof: Fail if one test fails, exiting the suite--load [filename]: Only load a specific yaml test specification, don't run all testsEnvironment variables:
PYTHONHASHSEED=0: this ensures that Sets etc return their entries in a deterministic orderMOCK_GMTIME=0: override time.gmtime() to use the value ‘0’ if none is providedThe above variables are useful for some tests to ensure reproducability. However using them may mask bugs in the code, so they should only be used where necessary.
Version 0.10 of Ponymail never detects format=flowed mails. This is because the content-type entry was not set up in msg_metadata As a consequence, some mails will be parsed differently. The test scripts allow for an alternate value for some tests.