| Age | Commit message (Collapse) | Author |
|---|
|
|
|
my goal here is also to start *real* unit tests for the keymanager, that
do not need an actual soledad implementation. this should make all the
coming tests much faster. I would like to have a common soledad stub
that follows the soledad api, but w/o actual disk persistance, and
migrate all the bulk of the keymanager tests to these unit tests.
|
|
- some pep8 problems
- some confusion with old and new code after merging
from old keymanager
|
|
disabled some tests that were failing, for some reason the twisted
logger doesn't want to be patched?
besides, I don't think it's a good idea to rely on log information for
tests. what is it really that we were trying to test there?
|
|
Port of the original commit:
8f1fe8dd4a54fd2bdda2fc78c339ce9b3d0fc331
by Zara Gebru that introduced updating keys in the background.
This was made in the legacy leapcode/keymanager repo, but was lost in
the merge to the unified bitmask-dev.
Original commit message follows:
--------------------------------
- refresh random key in random time
- add get key by fingerprint
- refactor nicknym methods to own file
- tests
- note this do not include a check for
revoked key, since that need some changes
in gnupg
- Related: #6089
|
|
This has been previously encapsulated in a dict, and the commands were
not modified accordingly.
I'm adding some very basic test for the KeymanagerService public api
contract.
- Resolves: #8577
|
|
in the variant that was merged, we call a failure method to get the
exception, so it's better to test a real failure initialized with an
exception.
besides, I'm starting to hate mocks.
|
|
This commit originall contained a fix for a wrong variable name that
avoided the outgoing service to be launched. This had been fixed in a
concurrent mr that got merged before this one. However, this MR
contained a couple of tests for the OutgoingService, and I'm merging
those tests now.
|
|
Missing yield from _insert_key_docs, which returns a Deferred, was
causing tests to fail.
|
|
Before we used to have content_doc.content_type = 'text/plain;
charset="utf-8"'.
Currently, we have content_doc.content_type = 'text/plain'.
This change will give us, on top of that: content_doc.charset = 'utf-8'.
One can reconstruct the original one using .content_type and .charset.
|
|
|
|
|
|
this is a port of commit 2d9bec78f in the legacy keymanager repo.
Additionally, I'm here separating benchmarking tests from the main tox
run.
In my machine several of these benchmarking tests seem to be broken, due
to issue https://github.com/isislovecruft/python-gnupg/issues/157
|
|
|
|
|
