Question
What are best practices designs for pre-release validation and testing before appgallery submission?
Short Answer
Every application submitted to Huawei AppGallery goes through a series of validation and quality checks to ensure that it meets the store’s standards and provides a seamless user experience. The quality of a developer’s pre-release testing significantly affects the review duration and approval rate. This article outlines the best practices for validation and testing before submitting an app to AppGallery.
Environment Setup & Configuration Validation
- Check whether you have created a release certficate before building APP
- Signed APP is must be signed with release .cer.
- All permissions used in the application must be clearly declared, and unused permissions must be removed.
- Min API / target API, compatibleSDKversion must be verified in order to prevent crashes.
- Orientation and aspect ratio issues must be tested across both rounded and rectangular devices.
Functional Test Best Practices
- All critical flows such as routing, login, signup, payments, QR scanning, and media playback should be tested end-to-end.
- Behavior during background/foreground, offline mode should be validated and tested.
- Edge case scenarios lise low ram, low battery mode must be tested.
- Apps behavior when permissions are rejected must be tested.
- Dark Mode and Light Mode of the device must be tested.
Performance & Stability Testing
- CPU load especially on wearable devices, FPS stability, and memory leaks should be tested using DevEco Profiler.
- Behavior on slow networks (2G/3G)
Security Validation
- Sensitive data (tokens, passwords) must not be stored in plain text.
- GDPR validation for the EU region
CI/CD Pipeline
- Code Checkout
- Static Code Analysis (Linter)
- Unit tests
- Signing
- App packaging
Applicable Scenarios
- When releasing a major version update
- Before publishing the app to AppGallery for the first time
- When adding support for new device categories
- When updating the application’s target compatible SDK
- Before enabling region-specific functionality
Top comments (0)