Feature #6301

Securely store secrets needed by the automated test suite

Added by bertagaz 2013-09-26 05:39:12 . Updated 2015-02-24 22:51:25 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Tails_1.3
Start date:
2013-09-26
Due date:
% Done:

100%

Feature Branch:
test/8188-better-test-suite-configuration
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

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.)

Subtasks

Related issues

Related to Tails - Feature #8188: Improve test suite configuration Resolved 2014-10-30
Related to Tails - Feature #8920: Have and use a repo shared between core developers for storing test suite secrets Resolved 2015-04-10
Blocks Tails - Feature #6304: Automate the most important bits of the Icedove tests Resolved 2013-09-26
Blocks Tails - Feature #6308: Write tests for SSH Resolved 2013-09-26

History

#1 Updated by intrigeri 2013-09-26 06:14:54

  • Target version set to Sustainability_M1

#2 Updated by intrigeri 2013-10-03 06:15:20

  • Subject changed from Way to securely store secrets to Securely store secrets needed by the automated test suite

#3 Updated by intrigeri 2015-01-06 13:00:29

  • blocks #8538 added

#4 Updated by anonym 2015-01-09 13:25:19

  • Assignee set to anonym
  • Target version changed from Sustainability_M1 to Tails_1.3.2

#5 Updated by anonym 2015-01-09 14:29:26

  • related to Feature #8188: Improve test suite configuration added

#6 Updated by anonym 2015-01-09 15:54:10

  • blocks Feature #6304: Automate the most important bits of the Icedove tests added

#7 Updated by anonym 2015-01-09 15:54:29

#8 Updated by anonym 2015-01-09 16:24:06

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 Feature #6300. Instead we want to use the approach outlined in the description of Feature #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.

#9 Updated by anonym 2015-01-10 16:35:06

  • Target version changed from Tails_1.3.2 to Tails_1.3

#10 Updated by anonym 2015-02-18 16:16:13

  • % Done changed from 0 to 50
  • Feature Branch set to test/8188-better-test-suite-configuration

#11 Updated by anonym 2015-02-19 09:04:13

  • Assignee changed from anonym to intrigeri
  • QA Check set to Ready for QA

#12 Updated by intrigeri 2015-02-19 12:35:53

  • Assignee changed from intrigeri to anonym
  • % Done changed from 50 to 70
  • QA Check changed from Ready for QA to Dev Needed

Same reason as Feature #8188.

#13 Updated by Tails 2015-02-19 15:24:12

  • Status changed from Confirmed to Fix committed
  • % Done changed from 70 to 100

Applied in changeset commit:76ecac141a98aeb343bcdf7f10b2fac52e3c6a89.

#14 Updated by intrigeri 2015-02-19 15:31:08

  • related to Feature #8920: Have and use a repo shared between core developers for storing test suite secrets added

#15 Updated by intrigeri 2015-02-19 15:32:17

  • Assignee deleted (anonym)
  • QA Check changed from Dev Needed to Pass

#16 Updated by BitingBird 2015-02-24 22:51:25

  • Status changed from Fix committed to Resolved