ck:test

Run unit, integration, end-to-end, and UI/visual tests with QA reporting.

Updated Aug 23, 2026

Search Tags:#testing #e2e tests #browser automation #ui automation #visual regression #coverage analysis #qa reporting

Ready to run

npx skills add https://github.com/MinhQuyen274/smartify --skill ck-test-minhquyen274

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ck:test
Source: https://github.com/MinhQuyen274/smartify/tree/main/Frontend_PROJECT_Figma/.opencode/skills/test
Command: npx skills add https://github.com/MinhQuyen274/smartify --skill ck-test-minhquyen274

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents broken releases by executing unit, integration, end-to-end, and UI/visual tests and then producing structured quality evidence for coverage and QA review.

Core Features & Use Cases

Test execution across scopes: Run code-level unit/integration/e2e suites and verify builds with coverage analysis.
UI/visual regression workflows: Generate browser-based UI test evidence using screenshot-driven checks (including responsive and accessibility-focused validation).
Actionable QA reporting: Output a structured report format that summarizes failures, coverage metrics, and recommendations.

Quick Start

Run ck:test with the relevant test scope to execute the appropriate unit/integration/e2e or UI test workflow and generate the QA outcomes.

Frequently Asked Questions about ck:test

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

FAQPage Schema

How do I run end-to-end and UI automation tests with structured QA reporting?▼

You can run end-to-end and UI automation tests by selecting the appropriate test scope to execute screenshot-driven browser workflows and generate a structured QA report summarizing failures and coverage metrics.

Can I validate code coverage thresholds and run unit tests for web release verification?▼

Yes, you can execute code-level unit and integration suites to verify builds, enforce strict coverage threshold validation, and ensure release quality by never ignoring failing tests.

What is visual regression testing and how does it handle accessibility checks?▼

Visual regression testing generates browser-based UI evidence using screenshot-driven checks, which includes responsive and accessibility-focused validation to prevent broken web releases.

Does browser automation work for regression testing after code changes?▼

Yes, browser automation fits workflows for regression after changes by running full test suites across unit, integration, end-to-end, and UI scopes to produce structured quality evidence.

What is the best way to generate actionable QA reports for failing tests?▼

The best way to generate actionable QA reports is to execute the referenced test workflows and use the provided report template to consistently summarize failures, coverage metrics, and recommendations.

Why does my build verification fail when tests are ignored?▼

Build verification fails because the testing workflow enforces a strict policy to never ignore failing tests, ensuring that all coverage thresholds and quality checks pass before release.