skills.rest
tonamson
tonamsonCOMMUNITY
Explore all skills by this author →
GitHub

ck:test

Orchestrate unit, integration, e2e, and UI tests and generate structured QA reports.

Updated Aug 23, 2026
Search Tags:#automation#ui#integration#e2e#qa#test#unit
One-click install
npx skills add https://github.com/tonamson/please-done --skill ck-test-tonamson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:test
Source: https://github.com/tonamson/please-done/tree/main/ck/.opencode/skills/test
Command: npx skills add https://github.com/tonamson/please-done --skill ck-test-tonamson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The skill streamlines the process of running comprehensive tests across unit, integration, end-to-end, and UI, consolidating results into a clear QA workflow.

Core Features & Use Cases

  • Orchestrates multi-layer test workflows (unit, integration, e2e, UI) with deterministic execution and unified reporting.
  • Generates coverage insights and QA reports for stakeholders, enabling faster release decisions.
  • Use Case: A developer pushes a feature branch and runs the full test plan to validate changes before merge and release.

Quick Start

Run the full test suite (unit, integration, e2e, and UI) and generate a structured QA report.

Frequently Asked Questions about ck:test

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

FAQPage Schema
How do I run automated tests across unit, integration, e2e, and UI layers?▼

To run automated tests across unit, integration, e2e, and UI layers, you can orchestrate the test commands to execute deterministically and collect the results into a unified workflow. This process consolidates multi-layer testing into a single automated execution.

What is the best way to generate QA reports for release decisions?▼

Generating QA reports for release decisions involves collecting test results and coverage insights to produce structured stakeholder summaries. This approach enables faster validation by consolidating multi-layer test outcomes into clear reports.

Can I use a single command to validate code quality before a merge?▼

You can validate code quality before a merge by executing a full test plan that covers unit, integration, e2e, and UI tests. This automatically orchestrates test commands and highlights failures before integration.

Does this test orchestration approach support coverage analysis across multiple environments?▼

This test orchestration approach supports coverage analysis across multiple environments by applying automated test execution and collecting structured results. It validates code quality consistently regardless of the specific environment setup.

Why do I need test orchestration for e2e and UI automation?▼

Test orchestration for e2e and UI automation is needed to streamline the execution of comprehensive test workflows and consolidate fragmented results. It ensures deterministic execution and unified reporting for complex multi-layer testing scenarios.

Related Skills

Explore More Software Engineering Skills→
RamblurrRamblurr

clojure-kaocha

Manage and execute Clojure test suites with Kaocha.

Community
Intermediate
qa-amanqa-aman
19

qa-metrics

Automate software quality metric measurement and reporting for sprint reviews.

Community
Advanced
RangeyRoverRangeyRover
3

speckit.tester

Automate test execution, coverage analysis, and reporting for code projects.

Community
Intermediate
DatTran26DatTran26

ck:test

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

Community
Advanced