| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | |
|
| |
|
|
|
| |
These tests were wrong they would always pass, even if the code
underneath was broken. With this fix they actually work.
|
| | |
|
| |
|
|
|
|
| |
This doesn't test the spawn path, which is a little bit more
complicated since it's running code in a thread instead of in the main
thread.
|
| |
|
|
|
| |
This decorates test methods that internally call a `cmd.apply()`,
which represents asynchronous code that returns a `twisted.deferred`.
|
| |
|
|
|
| |
These test only check if get_account_by_address is called correctly.
All other parts of `apply()` are left out.
|
| |
|
|
|
|
| |
This instantiates an actual Envelope object instead of a Mock object
for use in the tests for envelope commands. The tests then do not fail
when they hit implicit getters of the form envelope['From'].
|
| |\
| |
| | |
Fix issue 1113
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently anything except "user@domain" (such as
"User Name <user@domain>"), will not work with the sign command, because
settings.get_account_by_address wants just the "user@domain" bit, and we
don't split it.
Fixes #1113
|
| | |
| |
| |
| |
| | |
These tests exercise issue 1113, which has to do with extracting the
mail correctly from the 'From' header.
|
| | |
| |
| |
| |
| | |
I wrote these looking at a bug, but they turned out not to be helpful
there, but they should be useful all the same.
|
| | |
| |
| |
| |
| |
| | |
Currently it's possible to set sign_by_default without setting a default
key. This is obviously not a good plan for all sorts of reasons. This
fixes the two failing tests from the last commit.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds tests to exercise #1110.
These tests operated on a twisted async method, based on the
inlineCallbacks decorator (which creates a deferred, but looks like
synchronous code). The tests therefore have to use twisted's trial
module for unittest. These seem to operate mostly correctly using the
standard python unittest runner, pass and fail work right, but expected
failure does not. Instead of an expected failure, you get pass.
I really am not impressed with trial. After several hours of mucking
with it I never got it to run any tests, just spit out errors or do
nothing. pytest can run these tests just fine, and if we're going to
change test runner I'll again say that pytest is much nicer to work
with.
|
| |
|
|
| |
The test file is also renamed.
|
| |
|
|
| |
makes pylint happier to run tests, doesn't affect main pytest.
|
| | |
|
| |
|
|
|
|
|
|
| |
This fixes a bug in determine_sender where an account that did match but
did not have a realname set was "not found" in case force_realname was
set.
Helped-By: Pol Van Aubel <dev@polvanaubel.com>
|
| |
|
|
| |
The second test case exemplifies a bug in determine_sender.
|
| |
|
|
|
| |
Otherwise the next account in the for loop might have been returned if
the account was found to match with its last alias.
|
| |
|
|
|
| |
This test case exemplifies a bug in determine_sender. The address is
matched correctly but the wrong account is associated with it.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
There are a number of things pylint warns on that absolutely make sense
to fix in production code, but for unittests they either don't matter
(like naming variables "foo"), can't be fixed (TestCase methods that
don't use self because they use a mock assert), or the descriptive names
violate PEP8. These are annoying and create noise, so tell pylint to
ignore them.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
