Skip to content
cccskills
FreePublished on GitHub

cherry-regression-test

Run repeatable tests of Cherry Studio’s key workflows with Playwright, which checks application behavior through automated interactions. Collect results on macOS and Windows and produce English reports for release acceptance or development validation.

OriginalShow the original description

Run Cherry Studio critical-path system regression tasks through the repository-owned Playwright E2E workflow. Use for full regression, release acceptance, development-branch system validation, or a named cherry-regression-test task on GitHub-hosted macOS and Windows runners.

See how to install

Good for

  • Checking key workflows before a release
  • Validating application behavior on a development branch
  • Running regression tests for a specific task
  • Reviewing failures across macOS and Windows

Files included (1)

  • SKILL.md4.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Cherry Regression Test

Run deterministic Playwright E2E tests against one driver-owned Cherry Studio process per platform. The tested product includes Chat, Agents, MCP, Skills, knowledge bases, translation, image generation, and code tools; an LLM test agent does not control the test run.

CI contract

Use .github/workflows/e2e-regression-test.yml as the entry point. It:

  1. Resolves a trusted branch or release tag.
  2. Initializes an isolated directory under the GitHub runner temporary folder.
  3. Installs the application and the code tools under test.
  4. Launches one owned Electron process with CDP enabled.
  5. Runs the ten files in tests/e2e/regression/ from simple to complex.
  6. Continues after a failed phase so later results are still collected.
  7. Produces English platform and aggregate reports, then enforces the verdict.
  8. Stops only the Electron process recorded in the isolated run directory.

Do not add an LLM tool loop, MCP control server, turn limit, or a second Electron launch for each test. A restart is allowed only where the case contract explicitly verifies persistence or switches from the clean startup profile to the authenticated shared profile.

Configuration

The workflow reads these repository variables and secrets:

  • CHERRY_TEST_CUSTOM_PROVIDER_BASE_URL
  • CHERRY_TEST_CUSTOM_PROVIDER_ANTHROPIC_BASE_URL
  • CHERRY_TEST_CUSTOM_PROVIDER_API_KEY
  • CHERRY_TEST_CUSTOM_PROVIDER_CHAT_MODEL
  • CHERRY_TEST_CUSTOM_PROVIDER_EMBEDDING_BASE_URL
  • CHERRY_TEST_CUSTOM_PROVIDER_EMBEDDING_API_KEY
  • CHERRY_TEST_CUSTOM_PROVIDER_EMBEDDING_MODEL
  • CHERRY_TEST_CHERRYIN_CHAT_MODEL
  • CHERRY_TEST_CHERRYIN_IMAGE_MODEL
  • CHERRY_TEST_CHERRYIN_ACCOUNT
  • CHERRY_TEST_CHERRYIN_PASSWORD

The custom chat provider requires both URLs: CHERRY_TEST_CUSTOM_PROVIDER_BASE_URL fills OpenAI, and CHERRY_TEST_CUSTOM_PROVIDER_ANTHROPIC_BASE_URL fills Anthropic. Both endpoints share CHERRY_TEST_CUSTOM_PROVIDER_API_KEY.

Chat and embedding providers are independent. Never print literal credentials, write them to fixtures, attach them to Playwright artifacts, or pass them to an unrelated action.

Test organization

Read scenario organization and the controller contract before making changes.

Register each case from the manifest:

test(...caseDefinition('S-01'), async ({ mainWindow }) => {
  // Assert the user-visible outcome.
})

cases.ts owns case IDs, titles, task tags, phases, and capability requirements. The workflow accepts a task ID and delegates selection to the controller. Prefer accessible roles, labels, placeholders, test IDs, and visible text. Native dialogs and cross-application interactions must use the repository-owned helpers in systemAutomation.ts.

Record assertions in Playwright, not prose. The custom reporter writes case and phase status into run.json and feeds the English Markdown/JUnit reports. The fixture saves failure screenshots. Executor errors and interrupted phases block a passing verdict. Do not enable Playwright Trace for credential-bearing tests because action parameters can expose secrets. A passing result does not depend on a model's judgment.

Focused execution

With an initialized run directory and its owned Electron process running:

pnpm exec tsx scripts/e2e/regression/cli.ts run-phase \
  --run-dir /absolute/run-directory --phase 02-basic-features

The task selected when initializing the run determines which cases execute. For a Notes-only run, initialize with --task notes. Enumeration is read-only: set CHERRY_TEST_RUN_DIR to an absolute path, but no initialized run directory or running Electron process is required because --list does not execute fixtures.

CHERRY_TEST_RUN_DIR=/tmp/cherry-regression-list pnpm test:e2e:regression --list

Do not call the regression cleanup command for an Electron instance owned by cherry-electron-dev; cleanup is only for an app record created by this driver.

Verification when changing the framework

Run the focused script suite and enumerate Playwright cases:

pnpm exec vitest run --project scripts scripts/e2e/regression
CHERRY_TEST_RUN_DIR=/tmp/cherry-regression-list \
  pnpm test:e2e:regression --list
pnpm typecheck:e2e
pnpm test:lint

Do not use pnpm test or pnpm build:check for this focused workflow change.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

agent-notes

FreeSummary

Record durable Cherry Studio engineering decisions in Agent Notes. Determine which changes need a note, prepare specifications with verifiable acceptance criteria, and manage approval, implementation, rejection, and replacement while preserving the reasoning behind decisions.

  • Deciding whether a change needs a lasting decision record
  • Documenting bug fixes with significant tradeoffs
  • Preparing specifications for approval before implementation
CherryHQ/cherry-studio52.7KUpdated Oct 18, 2026

Get answers about Cherry Studio from the installed version’s product information. The skill explains features, settings locations, and shortcuts, provides clickable navigation entries, and helps diagnose connection failures, configuration problems, and runtime errors.

  • Finding a feature or settings page
  • Checking supported providers and default shortcuts
  • Diagnosing connection failures and runtime errors
CherryHQ/cherry-studio52.7KUpdated Oct 18, 2026

cherry-browser

FreeSummary

Operate the visible browser pane in a Cherry Studio conversation to navigate pages, click controls, fill forms, capture screenshots, and investigate browser issues. It can work with authenticated websites while checking page state and action outcomes.

  • Navigate and operate an authenticated website
  • Fill forms and verify the resulting page state
  • Capture screenshots of a page or specific section
CherryHQ/cherry-studio52.7KUpdated Oct 18, 2026

cherry-computer

FreeSummary

Operates native desktop apps through Cherry Studio Computer Use. It reads interface information, types, clicks, and captures windows, using fresh observations to choose actions and verify results within the permissions and capabilities available.

  • Open a desktop app and inspect its interface
  • Enter text and click controls in an app
  • Capture a window when interface details are unclear
CherryHQ/cherry-studio52.7KUpdated Oct 18, 2026

Develop and verify changes in a tracked Cherry Studio Electron instance, a running desktop app. Use real UI behavior, logs, and performance measurements to investigate problems, compare fixes, or test a pull request and report the results.

  • Implement UI changes and verify them in the app
  • Reproduce bugs and inspect runtime logs
  • Compare performance before and after a fix
CherryHQ/cherry-studio52.7KUpdated Oct 18, 2026

Search for and install skills that fill a missing capability, or open the Skills settings for management. When suitable options are unavailable, hand off to the built-in skill-creator and continue the original task.

  • Finding and installing a skill for a missing capability
  • Opening Skills settings to review installed skills
  • Opening Skills settings to uninstall a chosen skill
CherryHQ/cherry-studio52.7KUpdated Oct 18, 2026

See all skills by CherryHQ

Report a problem with this skill