e2e-bruno

Orchestrate end-to-end API testing workflows with Bruno collections and CI pipelines.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/333-333-333/agents --skill e2e-bruno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-bruno
Source: https://github.com/333-333-333/agents/tree/main/skills/e2e-bruno
Command: npx skills add https://github.com/333-333-333/agents --skill e2e-bruno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Bruno end-to-end API testing becomes organized and repeatable by structuring collections, environments, and CI-ready workflows with Bruno.

Core Features & Use Cases

  • Organize Bruno collections per service to keep tests maintainable.
  • Define reusable Bruno environments for local, development, and staging.
  • Publish and reuse test scripts, and integrate tests into CI pipelines.
  • Validate API endpoints automatically in headless runs.

Quick Start

Run Bruno E2E tests for all services locally to validate API endpoints and CI integration.

Frequently Asked Questions about e2e-bruno

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

FAQPage Schema
How do I integrate Bruno API testing into CI pipelines?

Organize Bruno collections per service and define reusable environments for local, development, and staging to keep end-to-end API tests maintainable. This structure prevents test clutter and ensures consistent execution across different deployment stages.

What do I need to run Bruno E2E tests in headless mode?

To run Bruno E2E tests in headless mode, you need the Bruno CLI installed, a Bruno workspace configuration file, per-service test files, and environment definitions. These components execute automated endpoint validation without a graphical interface.

How do I structure Bruno collections for microservices API testing?

Structure Bruno collections per service to maintain clear separation of API testing workflows. This organization isolates test scripts and environment definitions for each microservice, making E2E validation scalable and easier to manage.

Can I reuse test scripts across different Bruno environments?

Yes, you can publish and reuse test scripts across local, development, and staging Bruno environments. Defining reusable environments allows the same E2E API test scripts to validate endpoints consistently throughout your deployment pipeline.

Why validate API endpoints automatically in headless Bruno runs?

Validating API endpoints automatically in headless Bruno runs ensures consistent E2E test execution within CI pipelines. This automated validation catches endpoint regressions early without requiring manual intervention or a graphical desktop client.