원클릭으로 Manus에서 모든 스킬 실행

run-all-tests

스타2

포크0

업데이트2026년 4월 6일 09:32

Run the full Mongoose.gg test suite. Use when running all tests, validating regressions, checking backend + frontend together, or doing final verification before completion.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

mongoose84

mongoose84/mongoose.gg

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Run All Tests

Run the repository's verification flow in this order:

Backend tests — .NET xUnit/integration tests
Frontend unit tests — Vitest + Vue Test Utils
E2E tests — Playwright with the backend in E2E mode

Use this skill when the user asks to:

run all tests
validate a change before merge
do a full regression check
verify backend and frontend still pass together

Default Workflow

Step 1 — Run backend tests

# From server/
dotnet test Mongoose.Api.Tests/

Step 2 — Run frontend unit tests

# From client/
npm run test:unit

Step 3 — Run Playwright E2E tests

Start the API in a background terminal with E2E-friendly flags:

# From server/Mongoose.Api/
$env:Auth__AutoVerifyEmail="true"; $env:RateLimiting__Enabled="false"; $env:Email__DevMode="true"; dotnet run

Wait until the backend is responding on http://localhost:5164, then run:

# From client/
npm run test:e2e

Optional Variants

Quick regression check: run only Steps 1 and 2
Headed E2E debugging: npm run test:e2e:headed
Playwright UI mode: npm run test:e2e:ui
Open the last E2E report: npm run test:e2e:report

Reporting Rules

After each step, report:

the exact command that was run
whether it passed or failed
the fresh evidence (exit code, pass count, or failing test names)

Do not claim the suite passes without command output.

If one stage fails, report that failure clearly and ask whether to continue with the remaining stages.

Repo-Specific Notes

Backend test project: server/Mongoose.Api.Tests/Mongoose.Api.Tests.csproj
Frontend test command: client/package.json → npm run test:unit
E2E command: client/package.json → npm run test:e2e
Frontend dev server uses http://localhost:5174
Playwright artifacts are written to client/playwright-report/ and client/test-results/
If Firefox E2E becomes flaky, prefer deterministic readiness checks over networkidle

이 저장소의 다른 Skills

같은 저장소

diary

mongoose84/mongoose.gg

Project work diary. Use at session start to load context, or at session end to record what was done this session.

2026-06-032

feature-implementation

mongoose84/mongoose.gg

Use when implementing a feature from a completed spec in this .NET 10 Minimal API + Vue 3 project. Orchestrates architect, backend-developer, frontend-developer, test-writer, and code-reviewer with quality gates and fix loops.

2026-05-102

new-endpoint

mongoose84/mongoose.gg

Scaffold a new API endpoint with DTO, repository interface, and integration test. Use when creating a new endpoint, adding a new API route, or implementing a new feature endpoint.

2026-05-102

run-e2e-tests

mongoose84/mongoose.gg

Run Playwright E2E tests with backend in E2E mode. Use when running end-to-end tests, testing E2E, verifying user flows, or debugging Playwright failures.

2026-05-052

name	run-all-tests
description	Run the full Mongoose.gg test suite. Use when running all tests, validating regressions, checking backend + frontend together, or doing final verification before completion.
argument-hint	Optional: "full suite", "skip e2e", or a specific area to prioritize

Run All Tests

Run the repository's verification flow in this order:

Backend tests — .NET xUnit/integration tests
Frontend unit tests — Vitest + Vue Test Utils
E2E tests — Playwright with the backend in E2E mode

Use this skill when the user asks to:

run all tests
validate a change before merge
do a full regression check
verify backend and frontend still pass together

Default Workflow

Step 1 — Run backend tests

# From server/
dotnet test Mongoose.Api.Tests/

Step 2 — Run frontend unit tests

# From client/
npm run test:unit

Step 3 — Run Playwright E2E tests

Start the API in a background terminal with E2E-friendly flags:

# From server/Mongoose.Api/
$env:Auth__AutoVerifyEmail="true"; $env:RateLimiting__Enabled="false"; $env:Email__DevMode="true"; dotnet run

Wait until the backend is responding on http://localhost:5164, then run:

# From client/
npm run test:e2e

Optional Variants

Quick regression check: run only Steps 1 and 2
Headed E2E debugging: npm run test:e2e:headed
Playwright UI mode: npm run test:e2e:ui
Open the last E2E report: npm run test:e2e:report

Reporting Rules

After each step, report:

the exact command that was run
whether it passed or failed
the fresh evidence (exit code, pass count, or failing test names)

Do not claim the suite passes without command output.

If one stage fails, report that failure clearly and ask whether to continue with the remaining stages.

Repo-Specific Notes

Backend test project: server/Mongoose.Api.Tests/Mongoose.Api.Tests.csproj
Frontend test command: client/package.json → npm run test:unit
E2E command: client/package.json → npm run test:e2e
Frontend dev server uses http://localhost:5174
Playwright artifacts are written to client/playwright-report/ and client/test-results/
If Firefox E2E becomes flaky, prefer deterministic readiness checks over networkidle