Bug #16856

Use non-Riseup email for Thunderbird automated tests

Added by intrigeri 2019-07-06 10:57:21 . Updated 2020-05-12 13:37:41 .

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Email Client
Deliverable for:

Description

The test suite config we have in “shared-secrets” and the one used by our Jenkins workers all use Riseup email accounts for testing Thunderbird. Problem is, the config for Riseup is shipped with Thunderbird itself, so we effectively don’t test the network-based part of the Thunderbird account setup wizard, which worries me since 1. that’s the part we patch; 2. presumably we don’t test the most common use case.

Should we switch to non-Riseup email accounts for these tests?

Subtasks

Related issues

Related to Tails - Feature #6156: Upstream secure Thunderbird autoconfig wizard In Progress 2016-05-19

History

#1 Updated by intrigeri 2019-07-06 10:57:30

  • related to Feature #6156: Upstream secure Thunderbird autoconfig wizard added

#2 Updated by intrigeri 2019-07-06 10:57:58

I’d welcome feedback on this idea. In particular, I would love to hear what @anonym has to say :)

#3 Updated by intrigeri 2020-05-12 13:37:41

  • Subject changed from Consider using non-Riseup email for Thunderbird automated tests to Use non-Riseup email for Thunderbird automated tests
  • Type of work changed from Discuss to Code

I could not think of any reason, in favor of the current setup, that would outweigh the problem described here. Nobody chimed in, so let’s assume this is something we should do.