1 1. Bank Data Test Cases
- 1.1 1.1 GET /accounts
- 1.2 1.2 GET /accounts/{accountId}/transactions
2 2. Bank Service Test Cases
- 2.1 2.1 GET /payments/{paymentId}
3 3. Insurance Test Cases
4 4. Health Check Test Cases

The following test cases have been implemented in the Testing Tool:

Response code validations.
Response schema validations.
Response data validations.

The tests below are a subset of a broader range of tests. New tests will be introduced gradually as the Ozone Testing Tool is updated and new versions of CBUAE Open Finance Standards are released.

1. Bank Data Test Cases

1.1 GET /accounts

Scenario	Response	Expected outcome

Scenario	Response	Expected outcome
Valid accountIds are included as a query parameter, each with distinct SubTypes like CurrentAccount, Savings, and CreditCard for a retail user in Active status	200	Returns a 200 if all headers are valid and returns a record for each specified accountId including CurrentAccount, Savings, and CreditCard for a retail user with status 'Active' and validate correct accountType and accountSubType fields are populated for each accountId
No accounts found	200 with an empty array	Returns a 200 if all headers are valid no account information is found for the specified accountId
Missing accountIds query parameter	400	Fails with 400 if accountIds query param is missing

Header validations:

Requirement	Scenario	Response	Expected outcome

Requirement	Scenario	Response	Expected outcome
GET /accounts	Missing o3-psu-identifier header	400	fails with 400 if o3-psu-identifier is not specified
GET /accounts	Invalid o3-psu-identifier header - not a b64 encoded value	400	fails with 400 if o3-psu-identifier header is invalid - not a base 64 encoded value
GET /accounts	Invalid o3-psu-identifier header - value is base 64 encoded, but the decoded value is not valid JSON	400	fails with 400 if o3-psu-identifier header is invalid - not a valid json
GET /accounts	Invalid o3-psu-identifier header - the decoded value is valid JSON, but it lacks the userId parameter	400	fails with 400 if o3-psu-identifier header is invalid - the decoded value is valid JSON, but it lacks the userId parameter
GET /accounts	Missing o3-ozone-interaction-id header	400	fails with 400 if o3-ozone-interaction-id header is not specified
GET /accounts	Missing o3-api-operation header	400	fails with 400 if o3-api-operation header is not specified
GET /accounts	Missing o3-aspsp-id header (o3-provider-id)	400	fails with 400 if o3-aspsp-id header param is not specified
GET /accounts	Invalid o3-aspsp-id header (o3-provider-id)	400	fails with 400 if o3-provider-id header is invalid

1.2 GET /accounts/{accountId}/transactions

Scenario	Response	Expected outcome

Scenario	Response	Expected outcome
Valid accountId provided in the path parameter which has a list of transactions	200	Returns a 200 if all headers are valid and returns transactions of specified accountId

2. Bank Service Test Cases

2.1 GET /payments/{paymentId}

Scenario	Response	Expected outcome

Scenario

Response

Expected outcome

Inquire a 'Pending' Single Immediate domestic payment

Note: When conducting the tests as described above, the main goal is to verify that all payments in different statuses can be accessed with the accurate schema.

200 with payment details in the response

Returns a 200 with correct schema and in the response the payment status is 'Pending', and the paymentId matches the paymentId in the path parameter.

3. Insurance Test Cases

<TODO>

4. Health Check Test Cases