skills.rest
jbreel77888
jbreel77888COMMUNITY
Explore all skills by this author →
GitHub

ke2e-tests

Enforce end-to-end test coverage for Kortix HTTP API contract changes.

Updated Aug 27, 2026
Search Tags:#ci/cd#api development#test coverage#e2e testing#api testing#contract validation#ke2e
One-click install
npx skills add https://github.com/jbreel77888/Agent-AiNorx --skill ke2e-tests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ke2e-tests
Source: https://github.com/jbreel77888/Agent-AiNorx/tree/main/.claude/skills/ke2e-tests
Command: npx skills add https://github.com/jbreel77888/Agent-AiNorx --skill ke2e-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of untested API changes breaking production functionality by enforcing a mandatory test-as-source-of-truth workflow for all modifications to Kortix's HTTP API routes, status codes, auth gates, and request/response shapes.

Core Features & Use Cases

  • Test-as-Source-of-Truth Enforcement: Ensures all API contract changes are paired with matching end-to-end test flows, with a coverage gate preventing untested changes from being merged or deployed.
  • Live API Validation Guidance: Provides step-by-step instructions for writing test flows that validate HTTP behavior against a live deployed API, including handling auth principals, route templates, and assertion patterns.
  • Use Case: When a developer modifies an API endpoint's response shape, this Skill walks them through updating the end-to-end spec, regenerating the route manifest, adding the corresponding test flow, and confirming the coverage gate passes before opening a pull request.

Quick Start

Use the ke2e-tests skill to validate that your recent API route change is fully covered by an end-to-end test flow and passes the coverage gate before opening a pull request.

Frequently Asked Questions about ke2e-tests

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

FAQPage Schema
How do I prevent API contract drift when modifying HTTP routes and response shapes?▼

End-to-end API testing validates live deployed endpoints by running black-box test suites against actual services, enforcing a coverage gate that requires a 1:1 mapping between test flows and documented API behavior.

How do I validate API endpoint changes against a live deployed service?▼

When modifying an API endpoint's response shape, you must update the end-to-end spec, regenerate the route manifest, add the corresponding test flow, and confirm the coverage gate passes before merging to prevent untracked API contract drift.

Do I need a black-box test suite to enforce test coverage for CI/CD pipeline changes?▼

An end-to-end testing approach differs from isolated unit testing by validating the entire HTTP API contract—including auth gates, routes, and request/response shapes—against live deployed endpoints rather than mocked internal components.

Why should I use end-to-end testing for HTTP API contract validation instead of unit tests?▼

End-to-end testing validates the entire HTTP API contract—including auth gates, routes, and request/response shapes—against live deployed endpoints, whereas unit tests mock dependencies and can miss integration-level contract drift.

Related Skills

Explore More Software Engineering Skills→
marcocellomarcocello
10

coding-python-backend

Implement Python backend APIs with route-service-domain separation and pytest coverage.

Community
Advanced
WSJ40WSJ40

hara-stage2

Convert Stage 1 safety faults into vehicle-level hazard JSON entries per Function_ID.

Community
Intermediate
pwarnockpwarnock
2

testing-automation

Automate TypeScript test workflows with the Bun test runner.

Community
Intermediate
rsmdtrsmdt
381

testing-strategies

Design test suites and assess coverage using test pyramid principles across Jest and Pytest.

Community
Advanced