run-tests

Automate unit, integration, API contract, and end-to-end browser tests.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/mamu7211/feirb-mailclient --skill run-tests-mamu7211
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-tests
Source: https://github.com/mamu7211/feirb-mailclient/tree/main/.claude/skills/run-tests
Command: npx skills add https://github.com/mamu7211/feirb-mailclient --skill run-tests-mamu7211

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires dotnet, docker, playwright, bruno, and includes scripts (resource) components.

What problem does it solve?

This skill streamlines the complex process of verifying the Feirb mail client by orchestrating unit, integration, API contract, and end-to-end browser tests across multiple environments.

Core Features & Use Cases

  • Multi-Layer Testing: Supports rapid unit testing, contract-based API validation via Bruno, and full-stack E2E browser automation using Playwright.
  • Infrastructure Orchestration: Automatically manages Docker-based test environments including PostgreSQL, GreenMail, and API containers.
  • Use Case: Developers can verify the entire system integrity after a code change by running the full test suite in a containerized environment to ensure auth flows, mail processing, and UI components function correctly.

Quick Start

Execute the run-tests skill to trigger the full suite of unit, API, and end-to-end tests within the configured Docker environment.

Frequently Asked Questions about run-tests

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

FAQPage Schema
How do I automate end-to-end browser testing for a .NET mail client application?

You can automate multi-layer testing for a .NET application by executing unit, integration, and end-to-end tests together. This skill orchestrates Playwright browser automation and Bruno API contract validation within a containerized Docker environment to verify system reliability across backend and frontend components.

What is the best way to run API contract tests alongside integration tests in a CI-CD pipeline?

The best way to run API contract tests alongside integration tests is using Bruno for contract validation and Docker for infrastructure orchestration. This combination automatically manages test environments including PostgreSQL and GreenMail containers to verify backend services and mail processing flows.

Do I need Docker and Node.js to run Playwright tests on a dotnet project?

Yes, you need Docker, Node.js, and the .NET SDK to run Playwright tests on a dotnet project to orchestrate the full test lifecycle. Docker manages the containerized test infrastructure including PostgreSQL and GreenMail, while Node.js supports the browser automation dependencies.

How does infrastructure orchestration work for integration testing with PostgreSQL and GreenMail?

Infrastructure orchestration for integration testing works by automatically managing Docker-based test environments including PostgreSQL, GreenMail, and API containers. This setup allows developers to verify mail processing flows and system integrity in an isolated containerized environment after code changes.

Can I validate email client UI components and backend services in a single test run?

Yes, you can validate email client UI components and backend services in a single test run by executing the full test suite. This triggers unit, API contract, and end-to-end browser specifications simultaneously within the configured Docker environment to ensure complete system integrity.

Why does my automated test suite require a containerized environment to validate auth flows?

An automated test suite requires a containerized environment to validate auth flows because it needs isolated instances of PostgreSQL, GreenMail, and API containers. Containerization ensures consistent infrastructure orchestration so backend services and frontend components are tested reliably without external dependencies.