cherry-pr-test

Featured

Test Cherry Studio PRs by checking out the branch, launching the Electron app in debug mode, and running interactive UI tests via CDP.

Testing & QA 46,279 stars 4397 forks Updated today AGPL-3.0

Install

View on GitHub

Quality Score: 90/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Cherry Studio PR Test Automated PR testing workflow for Cherry Studio. Checks out a PR, launches the Electron app with Chrome DevTools Protocol, connects agent-browser, and runs interactive UI + code review tests. ## Prerequisites - `gh` CLI installed and authenticated - `agent-browser` installed (for CDP-based UI testing) - `pnpm` installed with project dependencies (`pnpm install`) ## Constraints - Always kill existing Cherry Studio processes before launching a new instance. - Never leave debug processes running after testing completes. - Always switch back to the default branch after testing. - Always show the test report to the user before posting it. ## Arguments `$ARGUMENTS` may contain: - A PR number (e.g., `13955`) - A PR URL (e.g., `https://github.com/CherryHQ/cherry-studio/pull/13955`) - Keywords like "latest", "recent" to pick a recent PR - Empty — list recent PRs and let the user choose ## Workflow ### Phase 1: Select & Checkout PR 1. If no PR number given, list recent open PRs: ```bash gh pr list --repo CherryHQ/cherry-studio --state open --limit 10 \ --json number,title,author,createdAt,headRefName,changedFiles \ --template '{{range .}}#{{.number}} | {{.title}} | by {{.author.login}} | files: {{.changedFiles}} {{end}}' ``` 2. Ask the user to pick one (or auto-pick if "latest"/"recent"). 3. View PR details to understand what changed: ```bash gh pr view <NUMBER> --json title,body,headRefName,files ``` 4. Checkout the PR b...

Details

Author
CherryHQ
Repository
CherryHQ/cherry-studio
Created
2 years ago
Last Updated
today
Language
TypeScript
License
AGPL-3.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category