-
Notifications
You must be signed in to change notification settings - Fork 378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Increase test coverage of MatrixTransport #3124
Labels
Comments
This was referenced Dec 5, 2018
Merged
ulope
changed the title
Write Unit and Integration Tests for Matrix
Increase test coverage of MatrixTransport
Jan 21, 2019
@hackaugusto I pulled your suggested tests into the issue description |
err508
pushed a commit
to err508/raiden
that referenced
this issue
Feb 1, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Feb 1, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Feb 1, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Feb 4, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Feb 5, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Feb 5, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Feb 5, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Feb 5, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Feb 5, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Feb 5, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Feb 5, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Feb 5, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Mar 8, 2019
condition: - Client A invites - The invite triggers _handle_invite in Client B's transport - Client A starts sending messages to Client B - Messages are lost, as the invite was not processed yet The race condition will be fixed in another PR. Appeared during raiden-network#3124, related raiden-network#2779, raiden-network#3123.
err508
pushed a commit
to err508/raiden
that referenced
this issue
Mar 13, 2019
condition: - Client A invites - The invite triggers _handle_invite in Client B's transport - Client A starts sending messages to Client B - Messages are lost, as the invite was not processed yet The race condition will be fixed in another PR. Appeared during raiden-network#3124, related raiden-network#2779, raiden-network#3123.
err508
pushed a commit
to err508/raiden
that referenced
this issue
Mar 14, 2019
condition: - Client A invites - The invite triggers _handle_invite in Client B's transport - Client A starts sending messages to Client B - Messages are lost, as the invite was not processed yet The race condition will be fixed in another PR. Appeared during raiden-network#3124, related raiden-network#2779, raiden-network#3123.
err508
pushed a commit
to err508/raiden
that referenced
this issue
Mar 18, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Mar 18, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Mar 18, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Mar 18, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Mar 18, 2019
condition: - Client A invites - The invite triggers _handle_invite in Client B's transport - Client A starts sending messages to Client B - Messages are lost, as the invite was not processed yet The race condition will be fixed in another PR. Appeared during raiden-network#3124, related raiden-network#2779, raiden-network#3123.
err508
pushed a commit
to err508/raiden
that referenced
this issue
Mar 27, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Mar 27, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Mar 27, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Mar 27, 2019
err508
pushed a commit
to err508/raiden
that referenced
this issue
Mar 27, 2019
condition: - Client A invites - The invite triggers _handle_invite in Client B's transport - Client A starts sending messages to Client B - Messages are lost, as the invite was not processed yet The race condition will be fixed in another PR. Appeared during raiden-network#3124, related raiden-network#2779, raiden-network#3123.
ulope
added a commit
to ulope/raiden
that referenced
this issue
Apr 18, 2019
- Extract the user/address mapping and presence handling into a separate utility class (`UserAddressManager`) - This allows the services to use this functionality as well (Fixes raiden-network#3720) - Complete unit test coverage of the new `UserAddressManager` Refs: raiden-network#3124, raiden-network#3252
ulope
added a commit
to ulope/raiden
that referenced
this issue
Apr 25, 2019
- Extract the user/address mapping and presence handling into a separate utility class (`UserAddressManager`) - This allows the services to use this functionality as well (Fixes raiden-network#3720) - Complete unit test coverage of the new `UserAddressManager` Refs: raiden-network#3124, raiden-network#3252
ulope
added a commit
to ulope/raiden
that referenced
this issue
Apr 25, 2019
- Extract the user/address mapping and presence handling into a separate utility class (`UserAddressManager`) - This allows the services to use this functionality as well (Fixes raiden-network#3720) - Complete unit test coverage of the new `UserAddressManager` Refs: raiden-network#3124, raiden-network#3252
@ulope I think you worked a lot on testing more. Can this be closed or should it be left open? |
Let's just close it, since this has been open a long time and has no specific coverage target. @ulope what you think? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Definition
Even though the
MatrixTransport
has a test coverage of > 70% most of that is incidental through the integration tests.We assumed that the integration tests would be enough to thoroughly test the transport, but it turns out that this assumption was mistaken.
We need specific tests that exercise esp. the unhappy and edge cases.
Some groundwork in that direction has already been laid with #3172 (and the accompanying tests)
Tests to write
Hanging transfers (Fix hanging transfers #3123)
User roaming
Account data update (Payments wait forever to be conducted #2779)
Misbehaving servers
Retries
The text was updated successfully, but these errors were encountered: