summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authoranonym <anonym@riseup.net>2017-02-04 15:37:23 +0100
committeranonym <anonym@riseup.net>2017-02-04 15:37:23 +0100
commit2d598c91735c6c8eeae3d02bb0188137e13d74b4 (patch)
tree408b4b2b1c277b4860d6ca1098b35f12a450fbd8
parentb0874d964ef76b4a786d3b8b4ec4368c953a2051 (diff)
Revert "Test suite: mark most of torified_gnupg as @fragile."test/12211-local-keyserver-onion
This reverts commit b0874d964ef76b4a786d3b8b4ec4368c953a2051.
-rw-r--r--features/torified_gnupg.feature10
1 files changed, 0 insertions, 10 deletions
diff --git a/features/torified_gnupg.feature b/features/torified_gnupg.feature
index 97ba265..cd044fb 100644
--- a/features/torified_gnupg.feature
+++ b/features/torified_gnupg.feature
@@ -12,30 +12,22 @@ Feature: Keyserver interaction with GnuPG
Scenario: Seahorse is configured to use the correct keyserver
Then Seahorse is configured to use the correct keyserver
- #12211
- @fragile
Scenario: Fetching OpenPGP keys using GnuPG should work and be done over Tor.
Given GnuPG uses the configured keyserver
When I fetch the "10CC5BC7" OpenPGP key using the GnuPG CLI
And the GnuPG fetch is successful
Then the "10CC5BC7" key is in the live user's public keyring
- #12211
- @fragile
Scenario: Fetching OpenPGP keys using Seahorse should work and be done over Tor.
When I fetch the "10CC5BC7" OpenPGP key using Seahorse
And the Seahorse operation is successful
Then the "10CC5BC7" key is in the live user's public keyring
- #12211
- @fragile
Scenario: Fetching OpenPGP keys using Seahorse via the OpenPGP Applet should work and be done over Tor.
When I fetch the "10CC5BC7" OpenPGP key using Seahorse via the OpenPGP Applet
And the Seahorse operation is successful
Then the "10CC5BC7" key is in the live user's public keyring
- #12211
- @fragile
Scenario: Syncing OpenPGP keys using Seahorse should work and be done over Tor.
Given I fetch the "10CC5BC7" OpenPGP key using the GnuPG CLI without any signatures
And the GnuPG fetch is successful
@@ -48,8 +40,6 @@ Feature: Keyserver interaction with GnuPG
And the Seahorse operation is successful
Then the key "10CC5BC7" has more than 2 signatures
- #12211
- @fragile
Scenario: Syncing OpenPGP keys using Seahorse started from the OpenPGP Applet should work and be done over Tor.
Given I fetch the "10CC5BC7" OpenPGP key using the GnuPG CLI without any signatures
And the GnuPG fetch is successful