e2e-varify

Analyze changes and augment e2e-impl-design.md with proposed test cases.

52|3|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill e2e-varify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-varify
Source: https://github.com/ZTE-AICloud/Co-OmniSpec/tree/main/skills/e2e-varify
Command: npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill e2e-varify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

该技能用于对端到端测试设计进行完整性检查和完善工作,分析测试实现报告,覆盖变更点、外部依赖异常场景以及测试数据设计。

Core Features & Use Cases

  • 自动检查变更点并对照设计和基线
  • 生成用例覆盖表并补充异常场景
  • 结合现有测试数据和实现报告,输出完善的测试实现分析

Quick Start

在已经准备好 spec、design、e2e-test 和 e2e-impl-design.md 的前提下,运行 e2e-varify 以开始完善测试设计。

Frequently Asked Questions about e2e-varify

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

FAQPage Schema
How do I verify end-to-end test design completeness against spec changes?

To verify end-to-end test design completeness, you need a tool that automatically checks spec changes against design baselines. This skill automates that by analyzing your design and test documents to confirm full coverage of recent changes.

What documents are required to automate end-to-end test coverage analysis?

End-to-end test coverage analysis requires four specific markdown files: spec.md, design.md, e2e-test.md, and e2e-impl-design.md. These documents provide the baseline specifications and implementation designs needed for analysis.

How do I generate test cases for external dependency exceptions in e2e testing?

Generating test cases for external dependency exceptions is handled by analyzing your existing e2e-impl-design.md. The skill automatically identifies gaps in exception scenarios and proposes structured test cases to augment your documentation.

Does the e2e test verification process output structured coverage tables?

Yes, the e2e test verification process outputs structured coverage tables. It updates your e2e-impl-design.md with structured sections including change logs, coverage tables, and data-design notes to document the analysis.

What is the best way to augment an existing e2e test implementation design?

The best way to augment an e2e test implementation design is to automate the comparison between spec changes and baseline tests. This skill analyzes the discrepancies and directly augments your design document with proposed test cases.