name: cherry-regression-test 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.
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:
- Resolves a trusted branch or release tag.
- Initializes an isolated directory under the GitHub runner temporary folder.
- Installs the application and the code tools under test.
- Launches one owned Electron process with CDP enabled.
- Runs the ten files in
tests/e2e/regression/from simple to complex. - Continues after a failed phase so later results are still collected.
- Produces English platform and aggregate reports, then enforces the verdict.
- 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.