ck:test

Automate unit, integration, end-to-end, and UI tests across multi-language stacks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dungnt97/wallet-portal --skill ck-test-dungnt97
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:test
Source: https://github.com/dungnt97/wallet-portal/tree/main/claude/skills/test
Command: npx skills add https://github.com/dungnt97/wallet-portal --skill ck-test-dungnt97

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating unit, integration, end-to-end, and UI tests across a software project is error-prone and time-consuming when done manually. This Skill consolidates testing workflows, ensures consistent validation, and provides a structured path from development to QA-ready releases.

Core Features & Use Cases

  • End-to-end test orchestration across code bases and languages, ensuring tests run reliably in CI and local environments.
  • Multi-language support (JavaScript/TypeScript, Python, Go, Rust, Flutter) with comprehensive test selection, parallelization, and result aggregation.
  • Structured QA reporting and coverage analysis to guide release decisions and improve code quality.

Quick Start

Run the default test flow to execute unit, integration, e2e, and UI tests for your project.

Frequently Asked Questions about ck:test

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

FAQPage Schema
How do I coordinate end-to-end tests across multiple programming languages?

You can coordinate end-to-end tests across multi-language stacks like JS/TS, Python, Go, Rust, and Flutter by automating test selection, parallelization, and result aggregation to ensure reliable execution in CI and local environments.

What is the best way to automate unit and integration testing workflows?

Automating unit and integration testing workflows is done by consolidating validation processes into a structured path. This ensures consistent execution, generates coverage reports, and provides deterministic results from development to QA-ready releases.

Can I run UI tests and e2e tests in parallel across different stacks?

Yes, you can run UI tests and e2e tests in parallel across different stacks. The automation supports comprehensive test selection and parallelization for languages like JavaScript, TypeScript, Python, Go, Rust, and Flutter, aggregating results for structured QA reporting.

Do I need standard test tooling and environment setup to generate QA reports?

Yes, standard test tooling and environment setup are required. The automation uses these prerequisites to apply execution constraints, validate tests, and output structured QA documentation and coverage analysis to guide release decisions.

How do I get deterministic results and coverage reporting for multi-language test automation?

Deterministic results and coverage reporting for multi-language test automation are generated by applying execution constraints and validations. The structured QA outputs and coverage analysis directly guide release decisions and improve overall code quality.