#
|
Test scenario |
Test description
|
Expected Result
|
Actual Test result (Pass/Fail) |
Comment
|
| |
|
|
|
|
|
| 1 |
Synchronous One-way messaging
|
Send a ping request to a service
|
Server returns an ack through the same channel
|
|
|
| |
|
Send 100 ping messages to a service
|
Server returns acks through the same channel |
|
|
| |
|
I. Send 100 ping messages to a service
II. Block the channel after sending 50 messages and wait 2 minutes. After that, restart the transport channel
|
Server retransmits remaining acks after establishing the channel
|
|
|
| |
|
I. Block the transport channel before receiving CreateSequenceResponse
II. After 2-3 minutes restart the channel |
Server retransmits CreateSequenceResponse after establishing the channel |
|
|
| 2 |
Asynchronous dual channel one-way messaging
|
Send a ping request to a service |
The first message to be sent on the "back channel" is CreateSequenceResponse.
All HTTP responses are 202 accepted messages.
Server responds through back channel
|
|
|
| |
|
Send 100 ping messages to a service |
The first message to be sent on the "back channel" is CreateSequenceResponse.
All HTTP responses are 202 accepted messages.
Server responds through back channel |
|
|
| |
|
I. Send 100 ping messages to a service
II. Block the request channel after sending 50 messages and wait 2 minutes. After that, restart the request channel
|
|
|
|
| |
|
I. Send 100 ping messages to a service
II. Block the back channel after sending 50 messages and wait 2 minutes. After that, restart back channel |
|
|
|
| |
|
I. Block the back channel before receiving CreateSequenceResponse
II. After 2-3 minutes restart back channel
|
|
|
|
|
| 3 |
Synchronous two way messaging
|
Send an echo request to a service
|
Server responds through the same channel attaching a sequence acknowledgement acknowledging the request received.
|
pass
|
|
| |
|
Send 100 echo requests to a service
|
Server responds through the same channel attaching a sequence acknowledgment acknowledging the request received so far. |
pass
|
|
| |
|
I. Send 100 echo requests to a service
II. Block the channel after sending 50 messages and wait 2 minutes. After that, restart the transport channel |
Server retransmits the remaining responses through the same channel.
|
pass
|
|
| |
|
I. Block the transport channel before receiving CreateSequenceResponseII. After 2-3 minutes restart the channel
|
Server retransmits CreateSequenceResponse after establishing the channel |
pass
|
|
| |
|
I. Do not set MercuryLastMessage property in client
II. Send an echo request |
Sequenceacknowledgement will be received for the application message. TerminateSequence message will not be sent. Client will stop after receiving the response.
|
Pass |
|
| |
|
Send a request to an inactive service
|
Create sequence messages will be transmitted to the service until it is activated
|
pass
|
|
| 4 |
Asynchronous two way messaging
|
Send an echo request to a service |
Server responds through back channel |
pass |
|
| |
|
Send 100 echo requests to a service |
|
pass |
|
| |
|
I. Send 100 echo requests to a service
II. Block the request channel after sending 50 messages and wait 2 minutes. After that, restart the request channel |
|
pass |
|
| |
|
I. Send 100 echo requests to a service
II. Block the back channel after sending 50 messages and wait 2 minutes. After that, restart back channel |
|
pass
|
|
| 5 |
Ordered delivery - Synchronous messaging
|
I. Write an echo service as follows.
public int echoInt(int x) { system.out.ln(x) ; return x; }
II. send 100 requests
|
Client should echo 1-100 sequentially.
|
pass |
|
| |
|
|
|
|
|
| |
Ordered delivery - Asynchronous messaging
|
I. Write an echo service as follows.
public int echoInt(int x) { system.out.ln(x) ; return x; }
II. send 100 requests |
Client should echo 1-100 sequentially. |
pass |
|
| 6 |
Module configuration
|
Configure the timing of acknowledgments in module.xml and verify with invoking a service
|
The acks should be generated in the defined time intervals
|
Fail
|
COMMONS - 63
|
| |
|
Configure rmsSequenceTimeout in module.xml
|
RM source (client) should get timed out within the specified time
|
|
|
| |
|
Configure rmdSequenceTimeout in module.xml
|
RM destination (server) should get timed out within the specified time |
|
|
| |
|
|
|
|
|
| 7 |
RM with MTOM encoding
|
I. Deploy a service which accepts a binary attachement (Use Axis2 MTOM sample service)
II. Write a client to send binary attachment reliably through network |
The attachment should be delivered successfully
|
Fail |
COMMONS-64 |
| |
|
|
|
|
|
