e2e-coverage

Verify end-to-end Breeze RMM coverage across UI, API, and agent layers using delta testing.

73|23|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/LanternOps/breeze --skill e2e-coverage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-coverage
Source: https://github.com/LanternOps/breeze/tree/main/.claude/skills/e2e-coverage
Command: npx skills add https://github.com/LanternOps/breeze --skill e2e-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies end-to-end Breeze RMM across UI/API/agent layers by testing only the delta since a baseline, enabling efficient release-readiness sweeps and partial-sweep resumption.

Core Features & Use Cases

  • Delta-based end-to-end verification: test changes since a baseline across UI, API, and agent layers.
  • Durable ledger and carry-forward: record results as PASS/FAIL/DEFERRED and carry forward unresolved items for subsequent sweeps.
  • Baseline and delta strategy: determine baseline tags, synthesize delta commits, and reuse a known-good environment recipe for each sweep.
  • Use Case: perform sweep after merging PRs to validate the combined impact before release; resume interrupted sweeps without re-testing already-cleared items.
  • Not intended for single-feature post-implementation checks; use feature-testing for targeted verification.

Quick Start

Start a delta-based sweep from the latest baseline and follow the runbook to execute baseline, delta, environment verification, classification, testing, and recording steps.

Frequently Asked Questions about e2e-coverage

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

FAQPage Schema
How do I verify end-to-end coverage across UI, API, and agent layers after merging multiple PRs?▼

Verify end-to-end coverage by applying delta testing to isolate changes since a baseline across UI, API, and agent layers. This approach validates the combined impact of multi-PR sweeps before release without retesting unchanged components.

Can I resume an interrupted end-to-end test sweep without re-testing already cleared items?▼

Delta testing optimizes release-readiness sweeps by extracting baseline tags and synthesizing delta commits. It tests only the changes since the baseline rather than the full suite, enabling efficient verification across broad multi-PR sweeps.

What is delta testing and how does it optimize release-readiness sweeps?▼

Delta testing optimizes release-readiness sweeps by extracting baseline tags and synthesizing delta commits to test only changes since the baseline. This avoids full suite execution and efficiently validates broad multi-PR impacts.

When should I use delta-based end-to-end checks instead of feature testing?▼

Use delta-based end-to-end checks for broad release-readiness sweeps across multiple layers, not for single-feature post-implementation checks. Delta testing targets combined impacts after merging PRs, whereas feature testing handles targeted verification.

How does the baseline and delta strategy work for environment verification?▼

The baseline and delta strategy determines baseline tags, synthesizes delta commits, and reuses a known-good environment recipe for each sweep. This structured workflow ensures accurate environment verification before item classification and test execution.

What results are recorded in the durable ledger during an end-to-end coverage sweep?▼

The durable ledger records end-to-end coverage sweep results as PASS, FAIL, or DEFERRED. This structured recording supports release readiness and carries forward unresolved items for subsequent sweeps.