TestingOps.ai

App markets · Native connection

Huawei AppGallery and TestingOps: comment insights for testing

AppGallery comments carry the APK version and phone model, which makes them useful for spotting a release that went wrong on particular devices. TestingOps reads them through an AppGallery Connect API client and writes insights and test ideas to the knowledge base.

  • Native connection
  • Available
Request a demo AppGallery Connect API: getting started
Connection
Native connection
Writes back
Nothing, it only reads
Last checked
7 Nov 2026

In short

Huawei AppGallery and TestingOps in short

The AppGallery connection reads your app's comments through the AppGallery Connect API with an API client (client ID and key), from the data site where the app's data is stored: Germany, Singapore, Russia or China.

The first sync reads the last 90 days for the countries you list, and each comment's rating, text, APK version, phone model and country feed the rating trend, the breakdowns and regression candidates between versions; with an AI model, TestingOps also writes themes and test ideas.

Nothing is written to AppGallery Connect and no replies are posted; the analysis tells you what to test, and running the tests is a separate step.

What it does

What it does for your testing

  1. 1

    APK versions become regression candidates

    Input
    Comments with their APK version
    TestingOps
    Compares each version with the previous one when both have at least 5 comments
    Output
    Versions whose average or 1–2 star share got worse, or, once the AI step has sorted the comments, whose crash share rose, with the reason
  2. 2

    Phone models become test targets

    Input
    The phone type of each comment
    TestingOps
    Breaks comments down by phone model, listing those with at least 2 comments
    Output
    The models to cover in device testing
  3. 3

    Comments become themes and test ideas

    Input
    Comment texts
    TestingOps
    With an AI model, sorts comments into themes and writes 2 to 4 test ideas per theme, with quotes from stored comments
    Output
    Theme sections in the project's knowledge base

Step by step

How it works

  1. Create an API clientIn AppGallery Connect, create an API client under Users and permissions → API key → Connect API with a role that can read comments, and note its client ID and key.
  2. ConnectUnder Integrations → App markets → App stores → AppGallery, enter the client ID and key, choose the data site where the app's data is stored and list the countries of that site (default tr).
  3. Link an appIn the project's Knowledge tab, add a source under App reviews and paste the App ID from App information in AppGallery Connect, or the AppGallery link.
  4. Comments are kept and maskedThe first sync reads up to 90 days; later syncs read from the last read minus 7 days. E-mail addresses and phone-like numbers are masked before storage.
  5. Insights are writtenThe statistics are rewritten on each sync; the AI step runs only for comments it has not seen.

Connect

Setup

  1. In AppGallery Connect, open Users and permissions → API key → Connect API and create an API client with a role that can read comments. Note the client ID and key.
  2. In TestingOps, open Integrations → App markets → App stores → AppGallery, enter the client ID and key, choose the data site and enter the countries, then select Test connection and Save.
  3. In the project's Knowledge tab, select Add source under App reviews and paste the App ID or the AppGallery link.
  4. Select Sync now. The first sync reads up to 90 days of comments.

Documentation: AppGallery Connect API: getting started

Where you connect it in TestingOps: Integrations → App markets → Huawei AppGallery

Use cases

Use cases

Catch a version that fails on some phones

Trigger
Ratings drop after a new APK version
Uses
The version breakdown, regression candidates and phone models
Agent activity
Reads the regression and crash sections before it plans device tests
Result
A test plan for the affected version and models
Condition
A version needs at least 5 comments to be compared

Test for the markets you serve

Trigger
The app is published in several countries of one data site
Uses
Comments of the listed countries with their country code
Agent activity
Compares themes and ratings by country
Result
Country-specific test ideas
Condition
The countries must belong to the chosen data site; another site needs another connection

Plan tests for recurring sign-in problems

Trigger
Comments about signing in keep appearing
Uses
The login theme's summary, test ideas and quotes
Agent activity
Writes test cases from the ideas
Result
Draft cases for the sign-in flow, ready for review
Condition
Draft cases straight from bug comments are available only through the TestingOps API, where they are tagged as Android cases

Capabilities

Capabilities and limits

What is read

  • Per comment: rating, content, APK version, phone type, country code and time; no title, language or OS version
  • Comments of the listed countries of one data site, up to 30 pages of 100 per sync; the first sync covers the last 90 days
  • Not read: reviewer names and IDs, and developer replies

What is produced

  • Overview: rating distribution and average, the last 30 days against the 30 before, and breakdowns by APK version, phone model and country
  • Versions and regressions: regression candidates between APK versions
  • With an AI model: theme sections with summaries, test ideas and quotes from stored comments

Where it can write

  • Nothing in AppGallery Connect; no replies to comments
  • In TestingOps: masked reviews, kept for 90 days and up to 2,000 per link, and the insight sections in the project's knowledge base

How it connects

AppGallery Connect API of the app's data site (Germany, Singapore, Russia or China), with a token from the same site for your API client

Account and permissions

  • An AppGallery Connect API client with a role that can read comments: client ID and key
  • The app's data site and country codes of that site

Limits

  • AppGallery comments carry no OS version or language, so those breakdowns stay empty
  • No app list API: Test connection checks the client, and you link the app by its App ID
  • The AI step sorts up to 300 new reviews per sync in batches of 100 and runs at most every 12 hours on automatic syncs (Sync now does not wait); it uses the project's AI model and your AI allowance, and without them only the statistics are written
  • Masking is pattern based: e-mail addresses and phone-like numbers are masked before storage, in what the AI step sees and in its output, but names or addresses typed into a review can remain
  • Review analysis does not test the app: test cases written from it run separately on an execution provider

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A team publishes its shopping app on AppGallery and links it with the countries it serves. After version 4.1.0, the Versions and regressions section shows the average more than half a star below 4.0.3, and most 1–2 star comments come from two phone models.

The crash theme's test ideas point to the checkout screen, so an agent plans checkout cases on those models, and the team runs them before publishing a fix.

Frequently asked questions

How far back are comments read?

The first sync reads the last 90 days. Later syncs read from the last read minus 7 days so that edited comments are caught, and comments older than 90 days are removed from the copy in TestingOps.

Which data site should we choose?

The one where your app's data is stored: Germany, Singapore, Russia or China. The token and the comments both come from that site, and the countries you list must belong to it.

Why is there no OS version breakdown?

AppGallery comments carry the APK version, phone model and country, but not the OS version or language, so those breakdowns stay empty.

Does TestingOps reply to comments?

No. It reads comments only and writes nothing to AppGallery Connect.

Do we need an AI model?

Not for the statistics and the rating-based regression candidates. Themes, summaries, test ideas and the crash-share signal need the project's AI model and count against your AI allowance; without them, the statistics are still written.

Next step

See what AppGallery comments say about your latest APK: request a demo and bring your App ID.

Request a demoMore app markets integrations