summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2020-02-04 08:10:20 +0000
committerintrigeri <intrigeri@boum.org>2020-02-04 08:10:20 +0000
commit57212d3c4b091aa386e14d581e011611dc4efa10 (patch)
treee2bbc7012b6b734515bca606e6abb9b58bc8f073
parent6b7c5e6a5e9ff308286da049d166c28b0f8ba0df (diff)
Revert "Test suite: remove Seahorse key synchronization scenarios"wip/bugfix/17169-seahorse-key-sync+force-all-tests
This reverts commit 6b7c5e6a5e9ff308286da049d166c28b0f8ba0df.
-rw-r--r--features/torified_gnupg.feature32
1 files changed, 32 insertions, 0 deletions
diff --git a/features/torified_gnupg.feature b/features/torified_gnupg.feature
index 9314bf3..31f898c 100644
--- a/features/torified_gnupg.feature
+++ b/features/torified_gnupg.feature
@@ -26,3 +26,35 @@ Feature: Keyserver interaction with GnuPG
When I fetch the "30F80A2C" OpenPGP key using Seahorse via the OpenPGP Applet
And the Seahorse operation is successful
Then the "DF841752B55CD97FDA4879B29E5B04F430F80A2C" key is in the live user's public keyring
+
+ #14770, #17169
+ @fragile
+ Scenario: Syncing OpenPGP keys using Seahorse should work and be done over Tor.
+ Given I fetch the "DF841752B55CD97FDA4879B29E5B04F430F80A2C" OpenPGP key using the GnuPG CLI
+ And the GnuPG fetch is successful
+ And the "DF841752B55CD97FDA4879B29E5B04F430F80A2C" key is in the live user's public keyring
+ And the key "DF841752B55CD97FDA4879B29E5B04F430F80A2C" has at least 1 subkey
+ And I delete the "85C7C1AAA3DFC34623B5516281119B9834AD5681" subkey from the live user's public keyring
+ And the key "DF841752B55CD97FDA4879B29E5B04F430F80A2C" has no subkey
+ When I start Seahorse
+ Then Seahorse has opened
+ And I enable key synchronization in Seahorse
+ And I synchronize keys in Seahorse
+ And the Seahorse operation is successful
+ Then the key "DF841752B55CD97FDA4879B29E5B04F430F80A2C" has at least 1 subkey
+
+ #14770, #17169
+ @fragile
+ Scenario: Syncing OpenPGP keys using Seahorse started from the OpenPGP Applet should work and be done over Tor.
+ Given I fetch the "DF841752B55CD97FDA4879B29E5B04F430F80A2C" OpenPGP key using the GnuPG CLI
+ And the GnuPG fetch is successful
+ And the "DF841752B55CD97FDA4879B29E5B04F430F80A2C" key is in the live user's public keyring
+ And the key "DF841752B55CD97FDA4879B29E5B04F430F80A2C" has at least 1 subkey
+ And I delete the "85C7C1AAA3DFC34623B5516281119B9834AD5681" subkey from the live user's public keyring
+ And the key "DF841752B55CD97FDA4879B29E5B04F430F80A2C" has no subkey
+ When I start Seahorse via the OpenPGP Applet
+ Then Seahorse has opened
+ And I enable key synchronization in Seahorse
+ And I synchronize keys in Seahorse
+ And the Seahorse operation is successful
+ Then the key "DF841752B55CD97FDA4879B29E5B04F430F80A2C" has at least 1 subkey