# FactQA sample delivery

Player journey · China / Vietnam / Thailand

This sample shows how a test report is organized. Scope, environments, execution volume and retest rounds are agreed before testing.

## 1. Scope and counting method

Initial build: 1.8.0 in a test environment. Payment steps use test accounts and a test payment environment.

Eight checkpoints: sign-in, verification code, KYC, deposits, payment return, withdrawals, game entry and bonus claims.

Six device / network combinations × eight checkpoints = 48 execution items.

38 passed, 6 failed, 4 blocked. In this sample, each failed item maps to one issue. In a project, issue counts and failed-item counts may differ. Repeat attempts and retests are counted separately.

| Market | Items | Passed | Failed | Blocked |
| --- | ---: | ---: | ---: | ---: |
| China | 16 | 12 | 3 | 1 |
| Vietnam | 16 | 14 | 1 | 1 |
| Thailand | 16 | 12 | 2 | 2 |
| Total | 48 | 38 | 6 | 4 |

## 2. Environments and execution distribution

| ID | City | Device / OS / browser | Network | Passed / failed / blocked |
| --- | --- | --- | --- | --- |
| CN-A | Shanghai | iPhone 13 / iOS 17 / Safari 17 | China Mobile 4G | 6 / 1 / 1 |
| CN-B | Shanghai | Windows 11 PC / Chrome 128 | China Telecom broadband | 6 / 2 / 0 |
| VN-A | Ho Chi Minh City | OPPO Reno11 / Android 14 / Chrome 128 | Viettel 4G | 6 / 1 / 1 |
| VN-B | Ho Chi Minh City | Windows 11 PC / Chrome 128 | FPT broadband | 8 / 0 / 0 |
| TH-A | Bangkok | iPhone 13 / iOS 17 / Safari 17 | AIS 4G | 5 / 1 / 2 |
| TH-B | Bangkok | Windows 11 PC / Chrome 128 | True broadband | 7 / 1 / 0 |

These combinations illustrate environment fields. Project availability is confirmed individually.

## 3. Issue list and suggested investigation

Priority definitions: P1 blocks a key journey or may mislead users about a transaction state; P2 materially affects a task but leaves a workaround; P3 affects display or guidance without blocking operation. Priorities are agreed according to project impact.

| ID | Priority | Environment / checkpoint | Observation | Suggested investigation |
| --- | --- | --- | --- | --- |
| CN-PAY-01 | P1 | CN-B / deposit | Test payment redirect remains on a loading screen without an outcome | Compare redirect requests, network records and timeout handling |
| CN-LOGIN-02 | P2 | CN-B / sign-in | An expired code leaves no resend action on the sign-in page | Review error state and resend flow |
| CN-UI-03 | P3 | CN-A / bonus claim | At 360 px width, the action label clips but the button still works | Review wrapping and width; retest adjacent sizes |
| VN-PAY-02 | P1 | VN-A / payment return | Payment page shows success; wallet retains its old balance | Review return-page refresh and order-state handling |
| TH-KYC-01 | P2 | TH-A / KYC | Oversized image triggers a generic error without size or format guidance | Review validation and Thai messages for valid and invalid files |
| TH-GAME-02 | P3 | TH-B / game entry | Retry guidance lacks Thai text; operation can continue | Check language resources and error-message coverage |

These are investigation directions based on observed behavior. Client or server logs, request records and further checks are needed to confirm technical causes.

## 4. Detailed issue · VN-PAY-02

Environment: VN-A. Initial build: 1.8.0.

Prerequisites: usable test account and payment channel; initial wallet balance recorded.

1. Sign in and open the wallet.
2. Initiate a deposit through the test payment channel.
3. Return to the wallet after the test payment page shows success.
4. Check the order state and wallet balance.

Expected: wallet balance and order state update according to the agreed product behavior.

Observed: in 3 of 5 independent attempts, the wallet retained its previous balance until a manual refresh. The other 2 attempts did not show the issue.

Impact: players cannot promptly confirm the deposit and may attempt it again.

Suggested investigation: compare order state and balance requests at payment return, verify that the page refreshes its data, then check server logs. Front-end behavior alone cannot distinguish caching, request timing or delayed server state.

Evidence index structure: EV-03 for a continuous payment-return recording; EV-04 for before-and-after balance screenshots. This sample illustrates index fields and includes no recording or screenshot files. Project deliveries link their evidence under the corresponding IDs.

## 5. Blocked items

| Environment / checkpoint | Blocker | Required condition |
| --- | --- | --- |
| CN-A / withdrawal | Test account lacks withdrawal permissions | Account with agreed permissions |
| VN-A / KYC | Accepted test identity sample unavailable | Agreed test materials |
| TH-A / withdrawal | Test bank channel disabled | Agreed test channel enabled |
| TH-A / bonus claim | Account does not meet eligibility requirements | Eligible test account |

Blocked work is neither passed nor failed. Execute it once prerequisites are available and record its outcome.

## 6. Retest · VN-PAY-02

Updated build supplied by the client: 1.8.1.

Retest environment: VN-A, keeping the device, OS, browser and network unchanged.

Repeat the steps in section 4 five times.

| Build | Attempts | Stale-balance occurrences |
| --- | ---: | ---: |
| 1.8.0 | 5 | 3 |
| 1.8.1 | 5 | 0 |

Result wording: no recurrence was observed during this retest. The result covers only the stated environment, build and attempts. Other combinations still require verification. It does not establish that the other five issues are fixed; initial results remain separate.

Retest evidence index: EV-R01, linked to a new recording and execution record in a project delivery.

## 7. Deliverables

Scope and environment matrix, execution records, issue list, screenshot and recording index, blockers and prerequisites, initial issue localization and investigation suggestions, and agreed retest results.

Observed facts, suspected causes and pending checks are recorded separately. Findings apply to the agreed build, environment and execution period.

## Optional competitive benchmarking

Compare your brand against selected brands in one market. See [the benchmark sample](benchmark-sample-en.md) for market-level timings, failures and differences.