| A | B | C | D | E | F | G | H | I | J | K | |
|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Project Name | Environment | |||||||||
2 | Tester's Name | Reviewed By | Salman | ||||||||
3 | Date Tested | Version | |||||||||
4 | Issue Id | Module | Issue Title | Description | Steps to Reproduce | Issue Type | Priority | Severity | Actual Result | Expected Result | Attachment |
5 | 1 | User Management | Weak password acceptance | System accepts vulnerable passwords (e.g., 1234) during user creation. | 1. Send POST request to create user. 2. Set password body as "1234". 3. Send Request. | Bug | Medium | Medium | System should enforce strong password policy (e.g., alphanumeric). | system should prompt to create strong password | bug1.png |
6 | 2 | User Management | NID accepts any length | System does not validate NID length or pattern. | 1. Send POST request. 2. Set 'NID' field to random length (e.g., 2 digits). 3. Send Request. | Improvement | Low | Low | NID must match the fixed pattern/length for the specific country. | NID must be of fixed pattern for a single country | NID.png |
7 | 3 | Send Money | Daily receive limit bypass | User can exceed daily receiving limits by emptying balance and receiving again. | 1. Send max limit (10k) to User A. 2. Withdraw/Empty User A balance. 3. Send 10k again to User A. 4. Repeat multiple times. | Bug | High | Critical | System must enforce a daily total receive limit, regardless of current balance. | A single transaction must have boundaries | |
8 | 4 | Agent Services | Inconsistent Deposit API (400 Error) | After multiple successful attempts, the system throws a 400 error for valid requests. | 1. Send Money to Agent successfully 3 times. 2. Attempt 4th transaction with valid data. | Bug | High | High | Transaction should process successfully or show specific error message. | Show the actual error for failed transaction | system.png |
9 | 5 | Transaction | Non-unique Transaction IDs | Transaction IDs are duplicated for specific time periods; not unique. | 1. Perform a transaction. 2. Call /transaction/search/{{trnxId}}. 3. Observe duplicate results. | Bug | High | Critical | Every transaction must generate a unique trnxID. | Each transaction should have unique trnxID. | trnx.png |