Skip to content

gplay testers set

Replace the authorized audience of --track with the Google Groups passed to --group. testers set is declarative: it replaces the WHOLE list (it maps 1:1 to testers.update — there is no add/remove). The testers resource exposes only Google Groups; individual tester emails are not supported by the API.

A bare set with neither --group nor --clear is refused (exit 2) so a forgotten --group can never silently wipe the list; empty the audience on purpose with --clear. There is no --confirm: a closed test track is low-stakes and reversible.

Writes inside an implicit Edit (open → testers.update → commit). Use --dry-run to validate and preview the payload without any HTTP call, and --keep-edit-on-failure to skip the auto-discard cleanup for debugging.

gplay testers set [flags]
FlagDescription
--clearreplace the tester list with an empty set (close the closed test)
--dry-runvalidate inputs and preview the tester list without any HTTP call
--group stringsGoogle Group email(s) authorized to test (repeatable or comma-separated)
--keep-edit-on-failureskip the auto-discard cleanup on failure (debug)
--output stringoutput format: table, json, or markdown (default: auto — table on TTY, json in pipes/CI)
--package stringAndroid package name (overrides .gplay/config.json pin)
--track stringtrack whose testers to replace (any closed-track name)
FlagDescription
--account stringname of a stored Account to use (overrides env and active Account)
--retry intretry transient failures (transport errors, 5xx, 429) up to N times with exponential backoff (default: 0, no retry)
--service-account stringpath to a service-account JSON, or inline JSON content (overrides --account, env, and active Account)
--timeout durationper-request API timeout, e.g. 30s or 2m (default: 60s for control-plane calls, none for uploads)
-v, --verboselog flow steps to stderr (info level)