testing

Orchestrates unit, API, browser, and database tests with structured JSON evidence output.

9|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ingpoc/SKILLS --skill testing-ingpoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/ingpoc/SKILLS/tree/main/testing
Command: npx skills add https://github.com/ingpoc/SKILLS --skill testing-ingpoc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Comprehensive testing orchestration and evidence collection to validate code changes, catch regressions, and streamline debugging across unit, API, browser, and database layers.

Core Features & Use Cases

  • End-to-end test orchestration for unit, API, browser, and database checks
  • Evidence collection with structured JSON outputs and exit-code semantics
  • CI/local development support with reusable scripts and templates
  • Real-world use case: run a full test suite on pull requests and publish evidence artifacts

Quick Start

Run the unit tests with the project's config, then collect all test evidence using the standard scripts.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I automate unit, API, and browser tests in a CI pipeline?

You orchestrate test suites across unit, API, browser, and database layers using automated scripts that execute checks and output structured JSON evidence artifacts with standard exit-code semantics for CI integration.

What is the best way to collect test evidence for pull requests?

Collect test evidence by running end-to-end test orchestration workflows that validate code changes and output structured JSON evidence artifacts summarizing unit, API, browser, and database check results for pull requests.

Can I run browser tests via Claude-in-Chrome MCP for pre-release validation?

Yes, browser tests execute via Claude-in-Chrome MCP as part of comprehensive testing workflows, systematically verifying functionality and collecting evidence for pre-release validation alongside unit, API, and database checks.

Does this testing workflow support both local development and CI pipelines?

Yes, comprehensive testing workflows support both local development and CI pipelines through reusable scripts and templates that orchestrate unit, API, browser, and database checks with structured evidence outputs.

Why do I need structured JSON outputs and exit-code semantics in test orchestration?

Structured JSON outputs and exit-code semantics in test orchestration provide machine-readable evidence artifacts and pass/fail signaling, streamlining debugging and enabling CI systems to gate releases on regression detection.