Test unsolicited response on dev environment

[em-abee]

Description

This ticket outlines testing of handling unsolicited messages in one of the environments of protocol server.

Expected Outcome

Protocol server should pass below test cases

Test Cases

1. If normal message comes before TTL, it should be received by BAP and queue should be cleared after 10 mins.
2. If normal message comes after TTL, It should not be sent ahead and dropped after logging correct message, queue should be cleared after 10 mins.
3. If normal message is never responded back, queue should be cleared after 10 mins.
4. If normal message comes after 10 mins, it is considered as unsolicited and should be sent to unsolicited webhook.
5. While BAP is waiting for solicited message of a type and in between comes unsolicited message of same type, BAP should not get confused between solicited and unsolicited messages.
6. If unsolicited message sent by BPP, it should reach the webhook.
7. Handling of unsolicited message while BAP server down.
8. Handling of unsolicited message while unsolicited webhook server down.

Mockups / Wireframes

NA

Product Name

Beckn

Domain

All

Tech Skills Needed

Strapi plugins, Message Queue Management, Webhook Integration

Complexity

High

Category

Testing

Sub Category

Unsolicited Message Handling

[em-abee]

Screenshot 1 illustrates the typical transmission of a 'status' request and response received by the BAP client within 10 seconds. Screenshot 2 demonstrates how the 'on_status' response with a random message ID is triggered from the BPP to the BPP network. Finally, Screenshot 3 depicts the reception of the same response on the BAP client.