DEV Community

HarmonyOS
HarmonyOS

Posted on

Best Practice Design for Pre-Release Validation and Testing Before AppGallery Submission

Read the original article:Best Practice Design for Pre-Release Validation and Testing Before AppGallery Submission

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

  1. Check whether you have created a release certficate before building APP
  2. Signed APP is must be signed with release .cer.
  3. All permissions used in the application must be clearly declared, and unused permissions must be removed.
  4. Min API / target API, compatibleSDKversion must be verified in order to prevent crashes.
  5. Orientation and aspect ratio issues must be tested across both rounded and rectangular devices.

Functional Test Best Practices

  1. All critical flows such as routing, login, signup, payments, QR scanning, and media playback should be tested end-to-end.
  2. Behavior during background/foreground, offline mode should be validated and tested.
  3. Edge case scenarios lise low ram, low battery mode must be tested.
  4. Apps behavior when permissions are rejected must be tested.
  5. Dark Mode and Light Mode of the device must be tested.

Performance & Stability Testing

  1. CPU load especially on wearable devices, FPS stability, and memory leaks should be tested using DevEco Profiler.
  2. Behavior on slow networks (2G/3G)

Security Validation

  1. Sensitive data (tokens, passwords) must not be stored in plain text.
  2. GDPR validation for the EU region

CI/CD Pipeline

  1. Code Checkout
  2. Static Code Analysis (Linter)
  3. Unit tests
  4. Signing
  5. 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

Written by Egemen Ayhan

Top comments (0)