e2e-runner

Run YAML-defined end-to-end API and database tests via CLI.

Updated Dec 15, 2025
One-click install
npx skills add https://github.com/liemle3893/go-tryve --skill e2e-runner-liemle3893
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-runner
Source: https://github.com/liemle3893/go-tryve/tree/main/skills/e2e-runner
Command: npx skills add https://github.com/liemle3893/go-tryve --skill e2e-runner-liemle3893

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

YAML-driven end-to-end testing for APIs and databases, enabling you to define and run tests without writing code, reducing manual test effort.

Core Features & Use Cases

  • YAML-based test definitions spanning setup, execute, verify, and teardown.
  • Multi-adapter support (HTTP, shell, PostgreSQL, MongoDB, Redis, EventHub, Kafka) for cross-system tests.
  • CLI tooling (init, run, validate, list, doc, install skills) and built-in functions for interpolation and assertions.
  • Real-world use case: Define an API user lifecycle test that creates a user via HTTP, validates it in PostgreSQL, and tears down resources.

Quick Start

Create a YAML test file and run it with the Tryve CLI to execute end-to-end tests immediately.

Frequently Asked Questions about e2e-runner

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

FAQPage Schema
How do I run end-to-end API and database tests using YAML?▼

You can run end-to-end API and database tests using YAML by defining test phases like setup, execute, verify, and teardown in a YAML file, then executing it via the CLI tool to automate validation without writing code.

Can I test across multiple databases and messaging systems in a single end-to-end test?▼

Yes, you can test across multiple databases and messaging systems in a single end-to-end test using built-in adapters for PostgreSQL, MongoDB, Redis, Kafka, EventHub, HTTP, and shell to validate cross-system integration scenarios.

What is the best way to validate an API user lifecycle without writing test code?▼

The best way to validate an API user lifecycle without writing test code is using YAML-driven definitions to create a user via HTTP, validate the record in PostgreSQL, and execute teardown commands to clean up resources automatically.

Does this YAML testing tool support CLI commands for validating and listing tests?▼

Yes, this YAML testing tool supports CLI commands for initializing, running, validating, listing, documenting, and installing tests, providing built-in interpolation and assertions to manage and report end-to-end test results.

How do I structure cross-system integration tests for APIs and databases?▼

You structure cross-system integration tests for APIs and databases by defining sequential phases—setup, execute, verify, and teardown—in a YAML schema, using adapters to interact with HTTP endpoints, shell commands, and various databases.