Feature #2111
msgr workloads
0%
Description
Develop the interfaces which will allow us to break messenger sockets at precisely-defined points.
Allow comparison between messages sent and received to verify correct transmission.
Write example tests to show how to use each capability.
History
#1 Updated by Sage Weil almost 11 years ago
- translation missing: en.field_story_points set to 5
- translation missing: en.field_position deleted (
2) - translation missing: en.field_position set to 2
#2 Updated by Sage Weil almost 11 years ago
- Target version set to v0.44
- translation missing: en.field_position deleted (
2) - translation missing: en.field_position set to 1151
#3 Updated by Sage Weil almost 11 years ago
- translation missing: en.field_position deleted (
1151) - translation missing: en.field_position set to 1141
#4 Updated by Greg Farnum almost 11 years ago
- Status changed from New to In Progress
- Assignee set to Greg Farnum
What we're looking for here are basic tests like connect, send message, kill connection, send another message; and verify that all the received messages are correct.
These tests aren't going to involve any serious internal Pipe state, but will require at least a barebones MessengerDriver and TestDriver interface. The outline is to implement 3 orders and 4 state/event reports:
orders: connect to y; send message x to y; break connection to y
reports: new incoming connection from y; finished establishing connection to y; received message x from y; connection to y broke
#5 Updated by Sage Weil almost 11 years ago
- Target version changed from v0.44 to v0.45
- translation missing: en.field_position deleted (
1150) - translation missing: en.field_position set to 8
#6 Updated by Sage Weil almost 11 years ago
- Target version changed from v0.45 to v0.46
#7 Updated by Greg Farnum almost 11 years ago
- Description updated (diff)
#8 Updated by Greg Farnum almost 11 years ago
- Status changed from In Progress to 4
I think the messenger tester may be at a point where we can call this bug satisfied.
#9 Updated by Sage Weil almost 11 years ago
- Target version deleted (
v0.46) - translation missing: en.field_position deleted (
67) - translation missing: en.field_position set to 9
#10 Updated by Sage Weil almost 11 years ago
- Target version set to v0.47
- translation missing: en.field_position deleted (
9) - translation missing: en.field_position set to 9
#11 Updated by Sage Weil almost 11 years ago
- Target version deleted (
v0.47) - translation missing: en.field_position deleted (
10) - translation missing: en.field_position set to 1
#12 Updated by Greg Farnum almost 11 years ago
- Status changed from 4 to Fix Under Review
- Assignee changed from Greg Farnum to Sage Weil
This has been sitting in my issue area for a while and it's distracting, so I'm reassigning for review. :)
#13 Updated by Sage Weil over 10 years ago
- translation missing: en.field_position deleted (
26) - translation missing: en.field_position set to 59
#14 Updated by Sage Weil over 10 years ago
- translation missing: en.field_position deleted (
117) - translation missing: en.field_position set to 129
#15 Updated by Sage Weil almost 10 years ago
- Assignee deleted (
Sage Weil)