ck:test

Execute unit, integration, e2e, and UI tests with coverage reports.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/DatTran26/KienTruThiHanh --skill ck-test-dattran26
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:test
Source: https://github.com/DatTran26/KienTruThiHanh/tree/main/.agents/skills/test
Command: npx skills add https://github.com/DatTran26/KienTruThiHanh --skill ck-test-dattran26

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Comprehensive testing across code, UI, and QA reporting to ensure reliable software delivery and visibility into quality metrics.

Core Features & Use Cases

  • Code-level testing: unit and integration tests to validate logic and interfaces.
  • UI/visual testing: browser-automated checks for visuals, accessibility, and regressions.
  • Quality reporting: generation of coverage reports and structured QA documentation for CI/CD.
  • Use Case: teams running nightly builds can automatically verify code health and surface defects early.

Quick Start

Run the default test suite to execute unit, integration, e2e, and UI tests across the project.

Frequently Asked Questions about ck:test

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

FAQPage Schema
How do I run unit and integration tests to validate code logic?

Run unit and integration tests using common test runners to validate logic and interfaces, then generate coverage reports to verify thresholds in development environments.

What's the best way to automate e2e and UI testing for visual regressions?

Automate e2e and UI testing through browser-automated checks to surface visual regressions and verify accessibility, ensuring software quality across the project.

Does this test automation approach support CI/CD pipelines?

Yes, this test automation supports CI environments by validating changes, generating structured QA documentation, and enforcing strict handling of failing tests during builds.

How do I generate QA reports and enforce coverage thresholds?

Generate structured QA reports and coverage metrics by executing comprehensive test suites, enforcing strict handling of failing tests, and verifying coverage thresholds.

Why do I need automated testing for nightly builds?

Automated testing for nightly builds verifies code health, surfaces defects early, and validates changes across unit, integration, e2e, and UI tests to ensure reliable delivery.

What happens when failing tests are encountered during test execution?

Failing tests trigger strict handling during test execution, halting progression and surfacing defects in the generated QA reports to maintain software quality standards.