run-tests

Run the Cartridge Controller monorepo test suite across linting, unit, build, and E2E checks.

80|49|Updated Mar 27, 2022
One-click install
npx skills add https://github.com/cartridge-gg/controller --skill run-tests-cartridge-gg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-tests
Source: https://github.com/cartridge-gg/controller/tree/main/.agents/skills/run-tests
Command: npx skills add https://github.com/cartridge-gg/controller --skill run-tests-cartridge-gg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run Tests provides a structured approach to validating changes by executing the Cartridge Controller monorepo's test suite, ensuring code quality and stability before commits or releases.

Core Features & Use Cases

  • Lint and format checks to ensure code quality before testing.
  • Run unit tests across packages (e.g., keychain, controller) and perform end-to-end tests where available.
  • Execute build and visual regression tests to verify integration and UI consistency.

Quick Start

Run the test suite locally to verify changes before committing.

Frequently Asked Questions about run-tests

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

FAQPage Schema
How do I run tests in a monorepo before committing changes?

To run tests in a monorepo before committing, execute the test suite locally to validate changes across linting, unit tests, storybook, builds, and e2e tests, ensuring code quality and stability.

How do I validate e2e and unit tests across different packages in a monorepo?

Validate e2e and unit tests across packages by coordinating commands like test, test:ci, and e2e. This provides a consistent workflow to verify code stability and integration across the project.

What is the best way to check linting and formatting before running a build?

The best way to check linting and formatting before a build is to run lint:check commands. This ensures code quality standards are met before executing build and visual regression tests.

Can I run storybook tests alongside unit tests in a CI workflow?

Yes, you can run storybook tests alongside unit tests in a CI workflow by coordinating test:storybook and test:ci commands, ensuring both UI consistency and code logic are validated.

Why does my test suite fail during local development?

Your test suite might fail during local development if lint:check, build, or e2e commands encounter code quality issues or integration errors, preventing code stability validation before commits.