Test Execution

Understanding the Test Suites

The GPAS test collection is organized into logical flows to ensure full coverage of the integration:

1. Successful Flows (Smoke Tests): Verifies that every method (Sessions, Balance, Debit, etc.) responds correctly to valid data and follows the Required Methods contract.

2. Error Handling (Edge Cases): Validates that your system correctly identifies and rejects invalid requests, returning the expected standard error codes (e.g., 1003 for duplicates, 1007 for insufficient funds).

3. Transactional Integrity (Full Flow): Simulates a real-player lifecycle: Session Init → Bet (Debit) → Win (Credit) → Reversal (Rollback). This ensures that balances are updated accurately at every step.

Performance Benchmark (SLA)

Response time is critical for user experience in gaming. During execution, Postman automatically monitors latency based on these tiers:

Status	Response Time	Action Required
✅ Passed	< 500 ms	Acceptable for production.
⚠️ Warning	501 ms - 700 ms	Review infrastructure/database latency.
❌ Failed	> 700 ms	Critically slow. Integration may be unstable.

Steps to Execute

1. Select Environment: Click the environment dropdown (top-right) and select GPAS_Wallet_Integration.
2. Open Collection Runner: Select the collection and click the Run button.
3. Execution Settings:
   • Delay: 0ms (to test concurrency).
   • Check: Ensure “Save response” is checked for debugging.
4. Run: Click Run GPAS Integration Tests.

Results Validation

Every request in the suite performs automated assertions:

• Status Validation: Matches the expected HTTP code (200, 400, etc.).
• Schema Validation: Verifies that the JSON structure is exactly as specified.
• Data Consistency: Checks that the balance returned after a credit is mathematically correct.

A successful test run must show 0 Failures. If even one test fails, the integration is not considered ready for certification.