tests

Name: tests
Availability: InStock
Author: ESPlotter

Route code changes to required and optional test suites across main, preload, and renderer boundaries.

Updated Aug 27, 2026

Search Tags:#integration #routing #e2e #strategy #regression #test #unit

Ready to run

npx skills add https://github.com/ESPlotter/ESPlotter --skill tests-esplotter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tests
Source: https://github.com/ESPlotter/ESPlotter/tree/main/.github/skills/tests
Command: npx skills add https://github.com/ESPlotter/ESPlotter --skill tests-esplotter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Routing and policy management for tests: it decides required test suites based on changes, defines optional escalation, and enforces regression rules.

Core Features & Use Cases

Routing-based test selection: maps changes to the appropriate test suites (unit, integration, and e2e).
Policy-driven regression rules: enforces coverage across boundaries and defines escalation paths.
Change-driven orchestration: coordinates main, preload, and renderer boundaries to ensure end-to-end validation.

Quick Start

Provide the list of changes and context, and the skill will output the recommended test suites and regression plan.

Frequently Asked Questions about tests

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

FAQPage Schema

How do I select the right test suites for code changes automatically?▼

Test routing maps code changes to the appropriate test suites by identifying boundary changes and enforcing regression rules. It evaluates feature changes, bug fixes, and refactors to output required unit, integration, and e2e suites.

What is test routing and how does it ensure regression coverage across boundaries?▼

Test routing is a policy-driven mechanism that maps main, preload, and renderer boundary changes to required test suites. It enforces regression and coverage rules to ensure end-to-end validation remains correct across infrastructure updates.

How do I determine which unit, integration, and e2e tests to run after a refactor?▼

Provide the list of changes and context to the routing algorithm. It identifies affected boundaries, maps them to required and optional test suites, and outputs a recommended regression plan covering unit, integration, and e2e levels.

Can I use test routing for infrastructure updates and feature changes across different boundaries?▼

Yes, test routing applies to feature changes, bug fixes, infrastructure updates, and refactors. It coordinates main, preload, and renderer boundaries to define required test suites and optional escalation paths for end-to-end validation.

Do I need to provide specific change context to get accurate test suite recommendations?▼

Yes, providing the list of changes and context is required for accurate test suite recommendations. The routing algorithm uses this input to identify boundary changes, map to required and optional test suites, and enforce regression rules.

What's the best way to enforce regression rules and coverage across main, preload, and renderer boundaries?▼

Use a policy-driven test routing approach that enforces coverage rules across main, preload, and renderer boundaries. It identifies boundary changes, maps them to required test suites, and defines optional escalation paths for regression validation.