- Move things to configuration file where appropriate (logging format, etc.).
- Rework execute_e2e_test signature to simplify it and get rid of keyword
arguments.
- Simplify output.
- Include a header comment in configuration file.
To let the user know that tests produce logs, include a message at the end of
the test output informing about locations of E2E and Mailgate logs.
Also, extract some constants.
Since it's not so easy to encrypt a message exactly the same way twice, we
only verify if the message has been encrypted or not.
Introduce minor changes to the library itself, because it doesn't work very
well with modern GnuPG.
Also, include GnuPG directory (pointed at by --homedir option).
- Use an environment variable to point at the configuration file while
strating gpg-mailgate.py.
- Unify paths: store temporary config, logs and anything else under 'test'
directory.
- Configure more tests (RSA, Ed25519).
- Add test descriptions to be shown before they're started.
Provide a simple Python script that would linsten on a given port and print to
standard output any message received via SMTP on that port.
This script will then be used to automatically test gpg-mailgate with different
scenarios (unknown recipient key, RSA key, elliptic curve key).
Piotr F. Mieszkowski