TestingOps.ai

App markets · Native connection

Google Play and TestingOps: review insights for Android testing

Play Console reviews show which app versions, phones and Android versions users struggle with. TestingOps collects them with a service account and turns them into insights and test ideas in the project's knowledge base.

  • Native connection
  • Available with limits
Request a demo Google Play Developer API: reviews
Connection
Native connection
Writes back
Nothing, it only reads
Last checked
7 Nov 2026

In short

Google Play and TestingOps in short

The Google Play connection reads your app's reviews through the Google Play Developer API with a service account key. Google's API returns only reviews written or changed in the last 7 days, so TestingOps keeps them from the first sync on and the history grows with each sync, up to 90 days.

From the stored reviews it calculates rating trends and breakdowns by app version, device, Android version and language, and flags regression candidates between versions; with an AI model it also sorts reviews into themes such as crashes or login and writes test ideas per theme.

Nothing is written to Google Play and no replies are posted, and the analysis points to what to test rather than testing the app.

What it does

What it does for your testing

  1. 1

    A bad release shows up as a regression candidate

    Input
    Reviews with their app version name or code
    TestingOps
    Compares each version with the previous one when both have at least 5 reviews: average down by 0.5 or more, 1–2 star share up 15 points, or, once the AI step has sorted the reviews, crash share up 10 points
    Output
    A Versions and regressions section that names the version and the reason
  2. 2

    Phones and Android versions become test targets

    Input
    The device (manufacturer and model) and Android version of each review
    TestingOps
    Breaks reviews down by device and by Android version, listing those with at least 2 reviews
    Output
    Devices and OS versions to put on the test plan
  3. 3

    Complaints become test ideas

    Input
    Review titles and texts
    TestingOps
    With an AI model, sorts each review once into one to three themes and writes a summary and 2 to 4 test ideas per theme, with quotes taken from stored reviews
    Output
    Theme sections such as Crashes and bugs or Login and account access in the knowledge base

Step by step

How it works

  1. Prepare a service accountCreate a service account key in a Google Cloud project with the Google Play Android Developer API enabled, and invite the service account in Play Console with access to the app.
  2. ConnectUnder Integrations → App markets → App stores → Google Play, paste the whole JSON key and the package names you want to pick from. Test connection checks the key against those packages.
  3. Link an appIn the project's Knowledge tab, add a source under App reviews and paste the Play link or the package name, for example com.example.app.
  4. Reviews are kept and maskedEach sync stores new and changed reviews, with e-mail addresses and phone-like numbers masked before storage. Reviewer names are never read.
  5. Insights are writtenThe statistics are rewritten on each sync; the AI step runs only when there are reviews it has not seen. The link shows how many reviews are kept and the state of the AI analysis.

The Overview section names the day the history starts, because Google's API never returns reviews older than a week.

Connect

Setup

  1. In Google Cloud, enable the Google Play Android Developer API for a project, create a service account and download its JSON key.
  2. In Play Console, invite the service account's e-mail under Users and permissions and give it access to the app.
  3. In TestingOps, open Integrations → App markets → App stores → Google Play, paste the whole JSON key, add the package names, then select Test connection and Save.
  4. In the project's Knowledge tab, select Add source under App reviews, paste the Play link or package name and select Sync now.

Documentation: Google Play Developer API: reviews

Where you connect it in TestingOps: Integrations → App markets → Google Play

Use cases

Use cases

Check a release after rollout

Trigger
A new version has been live for a few days
Uses
Reviews of the new and the previous version, and the crash theme
Agent activity
Reads the Versions and regressions section and the crash theme when it plans regression tests
Result
Test focus on the version, devices and themes that got worse
Condition
A version needs at least 5 reviews to be compared

Pick phones for the Android test plan

Trigger
A team plans which devices to test on
Uses
The device and Android version breakdowns
Agent activity
Suggests the devices and OS versions with many low ratings
Result
A device list backed by review counts
Condition
Only devices with at least 2 reviews are listed

Write cases for recurring complaints

Trigger
The same login or payment problem keeps coming up
Uses
The theme summary, test ideas and quotes
Agent activity
Writes test cases from the test ideas after checking the existing cases
Result
Draft cases for the reported problem, ready for review
Condition
Draft cases straight from bug reviews are available only through the TestingOps API, not from a button in the app

Capabilities

Capabilities and limits

What is read

  • Per review: star rating, title and text, reviewer language, app version name or code, device (manufacturer and model), Android version and last-modified time
  • Only reviews with text that were written or changed in the last 7 days, up to 20 pages of 100 per sync
  • 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 version, device, Android version and language
  • Versions and regressions: versions with at least 3 reviews and the regression candidates between them
  • With an AI model: one theme section per theme with a summary, 2 to 4 test ideas and quotes from stored reviews

Where it can write

  • Nothing in Google Play: no replies and no changes to the store listing
  • 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

Google Play Developer API with a service account key (JSON), exchanged for a token at Google's token endpoint

Account and permissions

  • A Google Cloud project with the Google Play Android Developer API enabled, and a service account key
  • The service account invited in Play Console with access to the app

Limits

  • History starts at the first sync because Google's API returns only the last 7 days; the 30-day comparison needs 60 days of history
  • No country breakdown: Google Play reviews carry the reviewer's language, not a country
  • Play has no app list API, so only the package names entered on the connection are offered
  • 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 ships version 5.2 of its Android banking app. Three weeks later, the Versions and regressions section shows 5.2 with an average 0.7 below 5.1 and a crash share more than 10 points higher, and the crash theme lists two phone models and Android 14 most often.

An agent reads the crash theme's test ideas, plans regression tests on those two models and that Android version, and writes the cases for review before the team runs them.

Frequently asked questions

Why do we see only a week of reviews at first?

Google Play's reviews API returns only reviews written or changed in the last 7 days. TestingOps keeps every review it reads, so the history grows with each sync, up to 90 days, and the Overview says on which day it starts.

Does TestingOps reply to reviews?

No. It only reads reviews. Nothing is posted to Google Play and the store listing is not changed.

Do we need an AI model for this?

Not for the statistics: rating trends, version, device and Android version breakdowns and the rating-based regression candidates are calculated without a model. Themes, theme summaries, test ideas and the crash-share signal need the project's AI model and count against your AI allowance.

Which personal data is stored?

Reviewer names and IDs are never read. E-mail addresses and phone-like numbers in the text are masked before storage; names or addresses typed into a review can still remain, because the masking is pattern based.

Can it write test cases from reviews?

The theme sections contain test ideas that agents use when they write cases. Draft test cases straight from bug reviews are available only through the TestingOps API; they are saved as unverified drafts in a folder for the app's reviews.

Does this test our Android app?

No. Review analysis tells you what to test next. The test cases are written separately and run on an execution provider.

Next step

See what your Play reviews say about your last release: request a demo and connect a Play Console app.

Request a demoMore app markets integrations