| Name | Verify Get Customer V1 |
|---|
| Category | COMMON |
|---|
| Execution Method | AUTOMATED (FAPI BIZA) |
|---|
| Preconditions | - All systems functional with no outages in progress
- Arrangement established with customer:basic scope
|
|---|
| Description | In this scenario Get Customer is called and verified. |
|---|
| Steps | - Using a token for an established arrangement containing appropriate permissions, initiate GET /common/customer
- Retrieve JSON payload and parse to ResponseCommonCustomer
- Verify semantic correctness of JSON payload for Get Customer
- Verify response in (2) has a generated x-fapi-interaction-id
- Execute (1) again supplying an x-fapi-interaction-id
- Validate the x-fapi-interaction-id header matches the one specified in (5)
- Execute GET /common/customer with x-v set to invalid. The request should be rejected with HTTP Status of 400 and a ResponseErrorList payload.
- Execute GET /common/customer with x-v set to 9999. The request should be rejected with HTTP Status of 406 and a ResponseErrorList payload.
|
|---|
| Inputs | Headers: - x-v = 1
- x-min-v = 1
- x-fapi-interaction-id where applicable
Parameters: |
|---|
| Expected Results | - Verify links validity ensuring self URL correctly references the payload
- Verify data object validity verifying semantic correctness of payload
- Verify that error responses for x-v headers are aligned
|
|---|