skills.rest
lettucebo
lettuceboCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gplay-testers-orchestration

Manage Google Play testing track testers and promote builds using gplay edit sessions.

Updated Mar 25, 2026
Search Tags:#release management#android#google play#gplay cli#testers#track promotion#edit session
One-click install
npx skills add https://github.com/lettucebo/Skills --skill gplay-testers-orchestration-lettucebo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gplay-testers-orchestration
Source: https://github.com/lettucebo/Skills/tree/main/skills/google-play-console-cli/gplay-testers-orchestration
Command: npx skills add https://github.com/lettucebo/Skills --skill gplay-testers-orchestration-lettucebo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Assigning testers to Google Play testing tracks and promoting builds between tracks requires precise CLI commands inside edit sessions, and mistakes like using nonexistent flags or forgetting to commit leave changes unapplied. ## Core Features & Use Cases - Tester Management: Read, replace, or merge tester sets on internal, alpha, beta, or custom closed tracks using emails or Google Groups. - Closed Track Creation: Create custom closed testing tracks and assign testers within a single edit session. - Build Promotion: Promote builds between tracks (e.g., internal to alpha, beta to production) with fractional staged rollout values. - Use Case: You need to onboard a QA team to a new closed track and roll out a build to 10% of production users; this Skill walks through creating the edit, uploading the AAB, assigning testers, and committing the session. ## Quick Start Ask the agent to assign a list of tester emails to the alpha track for your app package and commit the edit session.

Frequently Asked Questions about gplay-testers-orchestration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assign testers to a Google Play testing track?▼

Use gplay testers update inside an edit session with --track and --emails or --google-groups, then run gplay edits commit. There is no --testers flag on gplay release; tester assignment only takes effect after the edit is committed.

How to list testers on a Google Play track with gplay CLI?▼

Use gplay testers get with --package, --edit, and --track flags. There is no testers list subcommand; the get command reads the current tester set for the specified track.

What is the difference between gplay testers update and patch?▼

update replaces the entire tester set, removing any emails or groups not included. patch merges with the existing set, adding testers while preserving fields you omit. Use patch to add testers without dropping current ones.

How do I promote a build from internal to production on Google Play?▼

Use gplay promote with --from and --to flags, such as --from internal --to alpha. The --rollout flag accepts a fraction from 0.0 to 1.0, so 0.1 means a 10% staged rollout to production.

Why are my Google Play tester changes not taking effect?▼

Tester changes made inside an edit session are inert until you run gplay edits commit. Verify the edit ID is correct and the commit command succeeds before expecting changes to apply.

Related Skills

Explore More Software Engineering Skills→
tamtomtamtom
43

gplay-gradle-build

Automate Android app building, signing, and packaging with Gradle.

Community
Intermediate
nimadorostkarnimadorostkar
25

mobile-release

Standardize mobile release processes with staged rollouts and crash monitoring.

Community
Advanced
hanamizukihanamizuki
127

gplay-testers-orchestration

Manage Google Play beta testers across internal, closed, and open testing tracks.

Community
Advanced
PostalocityPostalocity
1

architect-tools

Automates system design decisions for complex software architectures.

Official
Advanced