Android app testing on China devices: scope and quote checklist

Build a device matrix from your users

• Choose device models, Android versions, manufacturer software versions and screen sizes using your target audience or release risks. Record mainland China or overseas device variants explicitly; a brand name alone is insufficient.
• Confirm the device location, system language, installation route and Google Mobile Services dependency. Ask suppliers to identify unavailable combinations and proposed substitutions before treating a matrix as covered.

Write tests for the intended China scenario

• Provide a versioned build and repeatable steps for installation, launch, login, permissions, core flows and recovery after interruption. State the expected screen or response for every case.
• Specify the permitted network, backend environment and regional dependencies. For notifications, payment or third-party login, agree authorized test accounts and test modes; successful device access alone proves none of these flows.

Choose who performs the testing

• Decide whether your team needs remote device access or a supplier to execute cases and investigate failures. Device access, scripted automation, manual testing and bug fixing are different scopes.
• Request an availability check and one sample case before the complete run. Confirm access permissions, permitted data, execution window, reporting language and who owns technical interpretation of failures.

Compare cost against recorded coverage

• Compare device access, executor time, environment setup, evidence preparation, retests, Chuzu coordination and applicable tax separately. Ask what happens to blocked cases and unused reserved time.
• Use devices × cases × runs as an illustrative coverage count, then list exclusions. Ten devices with one launch check are a different purchase from ten devices with complete login and transaction flows.

Accept evidence and close access

• Require pass, fail or blocked for every agreed case, with build identifier, model, OS, network, execution time and reproduction steps. Agree screenshots or logs while excluding sensitive user data.
• Agree retest limits and access removal or deletion records. Chuzu coordinates only the accepted scope; device supply and testing capability require project review, and a completed report does not guarantee a defect-free app.

Explore the project plan

Choose a specific resource