[QA-E2E-04] Writing Integration Tests for End-to-End B2B Ingestion Scenario

Testing and Automation

Published

October 14, 2026

NoteTask Brief
  • Component: E2E Testing Matrix.
  • Tools: Postman / Newman or Go Integration Tests.
  • Task Type: QA / Automation.
  • Status: Ready for Implementation

Task Description

It is necessary to cover the new B2B authorization and data publishing pipeline with automated tests to guarantee the integration correctness across three services (AuthService -> ProcessService -> Kafka).

Verification Scenarios (Test Cases)

  1. Test 1 (Valid Token): Send a POST request containing a correct token belonging to an active store. Expected result: HTTP 200 OK (or 202 Accepted). Verify that a corresponding JSON message featuring the correct store_id has appeared in the Kafka topic.
  2. Test 2 (Invalid Token): Send a request with a fake token. Expected result: HTTP 401 Unauthorized / gRPC code 16. The request must not be forwarded to Kafka.
  3. Test 3 (Suspended Store): Send a token belonging to a store with a SUSPENDED status. Expected result: Business error STORE_BLOCKED. The request must not be forwarded to Kafka.