From a52ec87d406379f1a6acd8d4f34605a4bac8683b Mon Sep 17 00:00:00 2001
From: Maximilian Krambach
Date: Tue, 3 Jul 2018 12:41:49 +0200
Subject: [PATCH] js: fixing Key import/export test
--
* BrowserTestExtension:
- The KeyImport/Export test had some errors, which have now been fixed
- The secret key used for the test examples is now placed more
prominently, and a clarification added that decrypt tests will not
work if this key is not imported.
* permittedOperations.js: typo
Thanks to rrenkert@intevation.de for the fixes
---
lang/js/BrowserTestExtension/index.html | 73 +++++++++++++++++++
.../tests/KeyImportExport.js | 25 ++++---
lang/js/src/permittedOperations.js | 2 +-
3 files changed, 87 insertions(+), 13 deletions(-)
diff --git a/lang/js/BrowserTestExtension/index.html b/lang/js/BrowserTestExtension/index.html
index 05d413ba..7f8d97de 100644
--- a/lang/js/BrowserTestExtension/index.html
+++ b/lang/js/BrowserTestExtension/index.html
@@ -23,6 +23,15 @@
The functionality tests, to be found in
gpgme/lang/js/BrowserTestExtension, check the overall functionality of
the standard packaged version of gpgmejs.
+
+
+ Most tests rely on a test gpg key to be available in gpg, which can be
+ found at the bottom of this page, or as "testkey.sec" in the
+ BrowserTestExtension's directory. Please import this key to your tested
+ gpg installation, or adapt the input defined in tests/inputvalues.js
+ if you want to use different values.
+
+
+
+
+
+
+
+