skills.rest
kangmomin
kangmominCOMMUNITY
Explore all skills by this author →
GitHub

e2e-test-mm

Automate end-to-end API testing for REST and gRPC services after code changes.

1|1|Updated Apr 9, 2026
Search Tags:#api#rest#e2e-testing#grpc#test-automation#data-seeding
One-click install
npx skills add https://github.com/kangmomin/harness-plugins --skill e2e-test-mm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-test-mm
Source: https://github.com/kangmomin/harness-plugins/tree/main/plugins/minmos-harness/skills/e2e-test-mm
Command: npx skills add https://github.com/kangmomin/harness-plugins --skill e2e-test-mm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After feature additions or modifications, this Skill performs end-to-end API tests to ensure related endpoints behave correctly and data integrity is maintained.

Core Features & Use Cases

  • End-to-end API test orchestration for REST and gRPC services after code changes.
  • Pre-flight checks, change impact analysis, edge-case coverage, and result reporting.
  • Automated data seeding, test isolation, and cleanup to protect existing data.

Quick Start

Execute an E2E test run for the latest changes to validate all impacted APIs.

Frequently Asked Questions about e2e-test-mm

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

FAQPage Schema
How do I automate E2E API tests for REST and gRPC services after code changes?▼

Run E2E API tests by orchestrating automated test execution against impacted REST and gRPC endpoints after feature changes. The process analyzes code changes, executes deterministic tests, and reports results while enforcing test isolation and preflight validation.

What is change impact analysis in end-to-end API testing?▼

Change impact analysis in E2E API testing identifies which REST and gRPC endpoints are affected by recent feature additions. It ensures targeted test execution, validating only the impacted APIs to maintain data integrity and correct behavior.

How do I prevent test data corruption during automated API testing?▼

Prevent test data corruption during automated API testing by enforcing test isolation, automated data seeding, and cleanup. This protects existing data by ensuring each E2E test executes within a controlled, deterministic environment.

Does this E2E testing approach support both REST and gRPC protocols?▼

Yes, this E2E testing approach supports both REST and gRPC protocols. It orchestrates end-to-end tests across both service types, analyzing impacted endpoints and executing deterministic validations after code modifications.

What are the limitations of automated E2E API test orchestration?▼

A limitation of automated E2E API test orchestration is its dependency on preflight validation and deterministic data seeding. Without proper test isolation and cleanup, tests may fail or cause unintended side effects to existing data.

Related Skills

Explore More Software Engineering Skills→
luyzkkluyzkk

api-design

Audit REST and real-time API endpoints for N+1, idempotency, and pagination risks.

Community
Advanced
hopeoverturehopeoverture
6

github-actions-ci-workflow

Generate GitHub Actions CI/CD workflows for web apps with lint, test, build, and deploy pipelines.

Community
Advanced
petrkindlmannpetrkindlmann
64

test-data-management

Generate deterministic, isolated test data with factories, anonymization, seeding, and cleanup.

Community
Advanced
avav25avav25
2

test-local

Validate prerequisites, run layered tests, and report local QA readiness.

Community
Intermediate