ck:test

Automate unit, integration, e2e, and UI tests across multiple runners.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/quanganh208/cookmate --skill ck-test-quanganh208
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:test
Source: https://github.com/quanganh208/cookmate/tree/main/.opencode/skills/test
Command: npx skills add https://github.com/quanganh208/cookmate --skill ck-test-quanganh208

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates comprehensive testing across unit, integration, e2e, and UI validation to reduce manual QA time and speed up feedback cycles.

Core Features & Use Cases

  • Test orchestration across multiple runtimes (Jest/Vitest, Pytest, go test, cargo test) to produce unified results.
  • CI integration for regression checks, coverage enforcement, and build verification.
  • UI/visual testing support with browser-based workflows and QA reporting.

Quick Start

Run the tests locally or via CI to validate code quality and detect regressions.

Frequently Asked Questions about ck:test

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

FAQPage Schema
How do I automate end-to-end testing across multiple test runners like Jest and Pytest?

You can automate end-to-end testing across Jest, Vitest, Pytest, go test, and cargo test by orchestrating runs across multiple runtimes to produce unified results and structured QA reports.

How do I integrate regression checks and coverage enforcement into my CI pipeline?

Regression checks and coverage enforcement in CI pipelines are handled by running automated test orchestration during builds to verify code quality and detect regressions.

What is the best way to coordinate UI testing and visual validation workflows?

UI testing and visual validation are coordinated through browser-based workflows that execute end-to-end UI layer tests and provide structured QA reporting for build verification.

Can I use this for local development testing or is it only for CI pipelines?

You can use this for local development testing as well as CI pipelines and QA sprints, applying automated end-to-end testing to reduce manual QA time and speed up feedback cycles.

Does this testing automation support unit and integration layers in addition to e2e?

Yes, this testing automation supports unit, integration, e2e, and UI validation layers, applying comprehensive test orchestration across your stack for regression and coverage verification.