run-tests — for Claude Code run-tests, feirb-mailclient, community, for Claude Code, ide skills, This spins up via, **postgres** (seeded with, bru run --env docker, npx playwright test, environment points to

v1.0.0

이 스킬 정보

적합한 상황: Ideal for AI agents that need execute tests for the feirb solution. there are three test layers:. 현지화된 요약: # Run Tests Execute tests for the Feirb solution. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

기능

Execute tests for the Feirb solution. There are three test layers:
Layer Framework Location Count What it covers
------- ----------- ---------- ------- ----------------
API (contract) Bruno tests/bruno/ 82 HTTP request/response contracts across 13 collections
E2E (browser) Playwright tests/playwright/tests/ 3 specs Auth flows, admin UI, component rendering

# Core Topics

mamu7211 mamu7211
[0]
[1]
Updated: 4/18/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
8/11
Quality Score
46
Canonical Locale
en
Detected Body Locale
en

적합한 상황: Ideal for AI agents that need execute tests for the feirb solution. there are three test layers:. 현지화된 요약: # Run Tests Execute tests for the Feirb solution. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

이 스킬을 사용하는 이유

추천 설명: run-tests helps agents execute tests for the feirb solution. there are three test layers:. Run Tests Execute tests for the Feirb solution. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

최적의 용도

적합한 상황: Ideal for AI agents that need execute tests for the feirb solution. there are three test layers:.

실행 가능한 사용 사례 for run-tests

사용 사례: Applying Execute tests for the Feirb solution. There are three test layers:
사용 사례: Applying Layer Framework Location Count What it covers
사용 사례: Applying ------- ----------- ---------- ------- ----------------

! 보안 및 제한 사항

  • 제한 사항: Bruno tests only (against running local API)
  • 제한 사항: Playwright tests only (against running local API)
  • 제한 사항: Requires repository-specific context from the skill documentation

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is run-tests?

적합한 상황: Ideal for AI agents that need execute tests for the feirb solution. there are three test layers:. 현지화된 요약: # Run Tests Execute tests for the Feirb solution. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

How do I install run-tests?

Run the command: npx killer-skills add mamu7211/feirb-mailclient/run-tests. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for run-tests?

Key use cases include: 사용 사례: Applying Execute tests for the Feirb solution. There are three test layers:, 사용 사례: Applying Layer Framework Location Count What it covers, 사용 사례: Applying ------- ----------- ---------- ------- ----------------.

Which IDEs are compatible with run-tests?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for run-tests?

제한 사항: Bruno tests only (against running local API). 제한 사항: Playwright tests only (against running local API). 제한 사항: Requires repository-specific context from the skill documentation.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add mamu7211/feirb-mailclient/run-tests. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use run-tests immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

run-tests

# Run Tests Execute tests for the Feirb solution. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows. Execute tests for the Feirb

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Run Tests

Execute tests for the Feirb solution. There are three test layers:

Test Layers

LayerFrameworkLocationCountWhat it covers
Unit / IntegrationxUnit + FluentAssertionstests/Feirb.Api.Tests/, tests/Feirb.Web.Tests/~300Endpoints, services, components, localization
API (contract)Brunotests/bruno/82HTTP request/response contracts across 13 collections
E2E (browser)Playwrighttests/playwright/tests/3 specsAuth flows, admin UI, component rendering

Running Tests

1. Unit + Integration tests (fast, no infrastructure needed)

bash
1# All .NET tests 2dotnet test Feirb.sln 3 4# Single project 5dotnet test tests/Feirb.Api.Tests 6 7# Filter by class or method name 8dotnet test --filter "ClassificationServiceTests" 9dotnet test --filter "Execute_AlreadyRunning_SkipsExecutionAsync"

2. Full stack tests (Bruno + Playwright in Docker)

Requires Docker or Podman. Builds API image, starts Postgres + GreenMail, runs Bruno API tests and Playwright E2E tests sequentially, then tears everything down.

bash
1tests/run-tests.sh

This spins up via tests/docker-compose.test.yml:

  • postgres (seeded with FEIRB_SEED_DATA)
  • greenmail (SMTP/IMAP mock with preloaded emails)
  • api (published .NET app on port 7273)
  • bruno (runs bru run --env docker)
  • playwright (runs npx playwright test in Chromium)

3. Bruno tests only (against running local API)

If the API is already running via Aspire / dev-harness:

bash
1cd tests/bruno 2npx @usebruno/cli run --env local

The local environment points to https://localhost:7272.

4. Playwright tests only (against running local API)

bash
1cd tests/playwright 2npx playwright test

Set BASE_URL environment variable if the API is not on the default port.

5. Interactive browser verification (against running local API)

Use /test-ui <path> <what to verify> for manual browser verification via Playwright MCP — visual checks, form interaction, and DOM assertions. Useful for debugging test failures or verifying features not covered by automated tests.

Reporting Results

  • Report number of tests passed, failed, skipped per layer
  • If tests fail: show failing test names, error messages, and identify relevant source code
  • For Bruno/Playwright failures in Docker: check tests/run-tests.sh exit codes and container logs

Bruno Test Collections

CollectionTestsCovers
01-auth10Login, register, refresh, password reset
02-setup3System initialization, SMTP/IMAP connectivity
03-admin-users8User CRUD, pagination, filters
04-admin-settings2System configuration
05-mail5Message listing, retrieval, authorization
06-settings-mailboxes7Mailbox CRUD
07-settings-profile8Profile management
08-admin-jobs5Job administration
08-settings-labels5Label CRUD
09-settings-preferences4User preferences
10-dashboard7Dashboard data
11-mail-stats2Email statistics
12-avatars9Avatar handling
13-settings-classification-rules6Classification rule CRUD

Playwright Specs

SpecSuitesCovers
auth.spec.ts3Setup, login/logout, error handling
admin-users.spec.ts7User table, badges, modals, permissions
person-chip.spec.ts7Component rendering, sizes, interactivity

관련 스킬

Looking for an alternative to run-tests or another community skill for your workflow? Explore these related open-source skills.

모두 보기

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
인공지능

widget-generator

Logo of f
f

prompts.chat 피드 시스템을 위한 사용자 지정 가능한 위젯 플러그인을 생성합니다

149.6k
0
인공지능

flags

Logo of vercel
vercel

리액트 프레임워크

138.4k
0
브라우저

pr-review

Logo of pytorch
pytorch

파이썬에서 텐서와 동적 신경망 구현 및 강력한 GPU 가속 지원

98.6k
0
개발자