gpgme/lang/js/test, branch javascript-bindingGnuPG Made Easy.http://git.bktus.com/gpgfrontend/gpgme/atom?h=javascript-binding2018-05-14T14:36:05Zjs: remove non-browser tests2018-05-14T14:36:05ZMaximilian Krambachmaximilian.krambach@intevation.de2018-05-14T14:36:05Zurn:sha1:d1ca90ef75aa4ab61cb8f7563be6fc55012a3900
--
* The majority of tests needs to be run in a nativeMessaging context.
Offering the few tests that don't need this context at two places
introduces issues with maintainability. All tests now removed can be
found in ./unittests.js
js: changed Key class stub2018-05-03T12:12:10ZMaximilian Krambachmaximilian.krambach@intevation.de2018-05-03T12:12:10Zurn:sha1:6f67814eb45725bc7f3736a2638bad0a7470f17a
--
* src/Key.js:
A Key object cannot offer more than basic functionality outside a
connection, so it now requires a connection to be present.
js: more testing2018-04-27T18:03:09ZMaximilian Krambachmaximilian.krambach@intevation.de2018-04-27T18:03:09Zurn:sha1:fda7b13f1b673962ce34b6f429158a7eb9cef47b
--
* Tests: initialization of the two modes, encryption
* gpgme.js: reintroduced message check before calling
Connection.post()
* gpgmejs_openpgp.js: Fixed openpgp mode not passing keys
* index.js: fixed some confusion in parseconfig()
* Inserted some TODO stubs for missing error handling
js: created TestExtension and smaller fixes2018-04-26T15:13:34ZMaximilian Krambachmaximilian.krambach@intevation.de2018-04-26T15:13:34Zurn:sha1:1f7b19512cfa7e1b153b99d6a2b40bad82a5496e
--
* Extensions:
- Moved testapplication to Demoextension
- Created BrowserTestExtension.
Includes mocha and chai. For running tests that cannot be run
outside a WebExtension
Both Extensions can be found zipped in build/extensions after
running build_extensions.sh
* Code changes:
- src/Config: Place for the configuration
- small fixes raised during testing in Keyring.js, Message.js,
- src/gpgmejs_openpgpjs.js don't offer direct GpgME object to the
outside, as it only causes confusion
- index.js init() now checks the config for validity
* Tests:
- Reordered tests in test/.
- Input values are now in a separate file which may be of use for
bulk testing
* moved the build directory from dist to build
js: First testing and improvements2018-04-25T17:45:39ZMaximilian Krambachmaximilian.krambach@intevation.de2018-04-25T17:45:39Zurn:sha1:3685913bf510a14b8cb324d980217d90489e6453
--
* Introduced Mocha/chai as testsuite. After development build
'npm test' should run the unit tests. Functionality exclusive to
Browsers/WebExtensions cannot be run this way, so some other testing
is still needed.
- package.json: Added required development packages
- .babelrc indirect configuration for mocha. ES6 transpiling
needs some babel configuration, but mocha has no setting for it.
- test/mocha.opts Vonfiguration for mocha runs
* Fixed errors:
- Helpers.js toKeyIdArray; isLongId is now exported
- Key.js Key constructor failed
- Message.js will not throw an Error during construction, a new
message is now created with createMessage, which can return an
Error or a GPGME_Message object
* Tests:
- test/Helpers: exports from Helpers.js, GPGME_Error handling
- test/Message: first init test with bad parameters