Cherry Regression Test logo

Cherry Regression Test

OrganizationPopular
CherryHQ
cherry-regression-test

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.

Overview

PublisherCherryHQ
Repositorycherry-studio
Skill namecherry-regression-test
Stars
52.5K
Forks
5.1K
Bundled files
Instructions only
LicenseAGPL-3.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by CherryHQ on GitHub. Read the source before you install it.

Installation

Install the Cherry Regression Test AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/CherryHQ/cherry-studio/tree/main/.agents/skills/cherry-regression-test
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/CherryHQ/cherry-studio.git /tmp/cherry-studio
mkdir -p .claude/skills
cp -r /tmp/cherry-studio/.agents/skills/cherry-regression-test .claude/skills/cherry-regression-test
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cherry Regression Test in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cherry Regression Test on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cherry Regression Test is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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:

ts
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:

bash
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.

bash
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:

bash
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.

Frequently asked questions

What does the Cherry Regression Test AI skill do?

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.

Why use Cherry Regression Test on TypingMind?

Because you install it once and use it with any model. Cherry Regression Test is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cherry Regression Test in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/CherryHQ/cherry-studio/tree/main/.agents/skills/cherry-regression-test. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Cherry Regression Test?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cherry Regression Test?

As many as you like. As long as a model supports skills, you can use Cherry Regression Test with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cherry Regression Test AI skill free?

Yes. It is published on GitHub by CherryHQ under the AGPL-3.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇