Test API Integration

Step 1: Click on 'Test' button

Step 2: Enter the relevant values in the field fields to begin testing

Step 3: Click on 'Test' and Verify the API test response

How to intepret the API Test responses?

Positive Test Cases (Expected to Pass)

• User Validation API Test

  • Purpose: Validates user authentication and authorization

  • What it tests: Sends a validation request to publisher API to verify user credentials

  • Expected: User is valid and can make purchases

• User Sync API Test

  • Purpose: Tests user synchronization between Coda and publisher

  • What it tests: Syncs user data to ensure consistency

  • Expected: User data is properly synchronized

• First Time Top-Up API Test

  • Purpose: Tests first-time purchase/top-up flow

  • What it tests: Simulates a new user making their first purchase

  • Expected: First-time purchase is successful

• Second Time Top-Up API Test

  • Purpose: Tests subsequent purchase/top-up flow

  • What it tests: Simulates an existing user making additional purchases

  • Expected: Repeat purchase is successful

Negative Test Cases (Expected to PASS if the response contain expected result with the correct error info else FAIL)

• Invalid UserId APITest

  • Purpose: Tests API behavior with invalid user IDs

  • What it tests: Sends requests with non-existent or malformed user IDs

  • Expected: API should reject the request with appropriate error

• Invalid User Validation APITest (method : topup on purpose to generate incorrect signature)

  • Purpose: Tests validation with invalid user credentials

  • What it tests: Sends validation requests with incorrect user data

  • Expected: API should reject invalid user validation

• Invalid SKU APITest

  • Purpose: Tests API behavior with invalid SKU codes

  • What it tests: Sends requests with non-existent or invalid SKU identifiers

  • Expected: API should reject invalid SKU requests

• InvalidTopUpAPITest (method : validate on purpose to generate incorrect signature)

  • Purpose: Tests top-up flow with invalid parameters

  • What it tests: Sends top-up requests with invalid payment data

  • Expected: API should reject invalid top-up requests

Miscellaneous Test Cases

• Serverlist API Test

  • Purpose: Tests server list retrieval functionality

  • What it tests: Validates that the correct server list is returned for a given game

  • Expected: Server list contains the expected server IDs and names