Feature #6298: Write more automated tests
Securely store secrets needed by the automated test suite
In our test suite we use access to email accounts or XMPP chat. We should be able to store that kins of credentials or other sensitive data (host/port/setting/keys/certificates for smtp, pop, imap, ssh/sftp, git, etc.)
#8 Updated by anonym about 5 years ago
When it comes to testing some arbitrary service, like SSH, Git, IMAP/POP/SMTP, we've decided against the "throw-away service" approach described in #6300. Instead we want to use the approach outlined in the description of #8188 instead, i.e. to store host/port/credentials/etc for the service as secrets. It will be up to the user to either setup such a service, or find a public one (e.g. register an email account with POP/SMTP/IMAP support), and then configure the appropriate secrets. We may want to tag such scenarios as
@registered-service or similar and make it easy to skip such scenarios (i.e. adding an option to
run_test_suite) for users that do not want to bother with this.