GAP — How to Run Test Cases
Test cases are used to determine how much load a server can support.
General Test Cases
- All – Selects all test cases to run a comprehensive validation.
- Balance – Checks if the correct balance is returned for the user.
- Loss Result – Validates if the loss is recorded correctly when a bet is lost.
- Win Result – Ensures the correct processing of winnings after a successful bet.
- Wallet Stress Test – Simulates multiple transactions in a short period to check system stability.
Transaction Rollback Scenarios
- Rollback – Tests the rollback of a transaction when required.
- Non-Existing Transactions Rollback – Attempts to roll back a transaction that does not exist.
- Duplicate Rollback – Ensures that duplicate rollback requests do not get processed multiple times.
- Already Rolled Back – Tests the behavior when trying to roll back an already rolled-back transaction.
- Win After Rollback – Validates if a winning transaction is correctly handled after a rollback.
Invalid Transaction Scenarios
- Bet With Negative Amount – Ensures the system rejects bets with negative amounts.
- Zero Amount Bet – Tests whether a bet with a zero amount is handled correctly.
- Insufficient Bet Amount – Validates if the system prevents bets when the amount is insufficient.
- Nullable Parameters – Tests system behavior when some required parameters are null.
Duplicate Transaction Scenarios
- Duplicate Bet – Ensures that a duplicate bet request is not processed twice.
- Duplicate Win – Checks if a win result is not duplicated for the same bet.
- Duplicate Rollback – Validates the prevention of duplicate rollback requests.
Non-Existing Transaction Scenarios
- Non-Existing Transactions Win – Tests if the system properly handles win results for non-existing bets.
Multiple Transaction Scenarios
- Multi Credit – Tests multiple credit transactions for the same user.
- Multiple Bet – Validates if multiple bets are processed correctly.
- Multiple Win – Ensures multiple wins are processed correctly for different bets.
Invalid and Edge Case Scenarios
- Random Key – Tests system behavior with a random or unknown key.
- Invalid Signature – Validates the security mechanism by checking how an invalid signature is handled.
- Failed Bet in Valid Round – Ensures failed bets in a valid game round are handled appropriately.
Performance & Load Testing
- 50 Requests in a Minute – Simulates 50 requests per minute to test system performance.
- 100 Requests in a Minute – Simulates 100 requests per minute to test system load.
- 150 Requests in a Minute – Tests the system's ability to handle 150 requests in a minute.
- 200 Requests in a Minute – Evaluates performance under a high request rate.
Example
Sample Response for each Test case: https://tinyurl.com/sampletestcasesgap
How to Run Test Cases in GAP Test Cases Panel
1. Access the Test Cases Panel
- Open your browser and navigate to the GAP BackOffice using this url: https://dev.dreamdelhi.com/login.
- Log in with your credentials which is provided by GAP.
- Navigate to Administration → Test Cases from the left-side menu.
2. Select Test Cases
- You can manually select one or multiple test cases by checking the corresponding checkboxes.
- If you want to run stress test cases, select the "All" checkbox.
3. Enter Required Details
- User ID – Enter the user ID for whom the test cases should be executed.
- Game ID – Enter the game ID, the gameid is taken from gameslist, provided by GAP.
- Token – Provide a valid authentication token.
- Email ID – Enter a valid email ID to receive test results.
- NOTE - Need to run all test cases then you need to enter valid email Id for sending testcase results.
4. Execute the Test Cases
- Click on the "Apply" button to initiate the normal test case execution without stress test cases.
- Click on the "Enter Email" button to initiate run the all test cases execution.
5. Monitor the Results
- Once executed, the system will process the test cases and return the results.
- You can check the logs or responses to verify the outcome of each test.
6. Verify Response and Logs
- Each test case will return a response indicating success, failure, or error details.
- If a test case fails, check the logs for error messages and validation failures.
- Some test cases may require multiple attempts to reproduce certain conditions.
7. Running Stress Test Cases (High Requests Per Minute)
- For test cases like "Wallet Stress Test", "50 Requests in a Minute", "100 Requests in a Minute", "150 Requests in a Minute", and "200 Requests in a Minute", the system will send bulk requests to check system stability.
- Monitor the server performance and response time when running these test cases.
8. Example
Sample Response for each Test case: https://tinyurl.com/sampletestcasesgap