메뉴
PPDS test conventions — which test framework to use per area, trait categories, file placement, coverage bar. Use when writing or organizing tests across .NET, TypeScript, or MCP code.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Cut a PPDS release — CHANGELOG refresh, version bump, tag push sequence, CI monitoring, post-publish verification. Use when preparing a new prerelease or stable release across CLI, TUI, MCP, Extension, and NuGet libraries.
Triage and merge open dependabot PRs per docs/MERGE-POLICY.md — classify each PR (auto-merge / verify-then-merge / manual review), enable auto-merge for safe ones, run targeted test suites for risky ones, and surface anything needing human judgment. Use when there's a backlog of dependabot PRs, after a quiet period, or as a routine drain.
AI self-verification of implemented work across surfaces (extension, CLI, MCP, TUI, workflow). Use after implementation to verify code works in its runtime environment.
Create, triage, and manage GitHub issues per PPDS backlog conventions. Use when creating issues, grooming the backlog, reviewing what to work on next, or filing bugs.
Brainstorm ideas into specs and plans through collaborative dialogue. Use when starting a new feature, exploring an idea, or designing a system — before any implementation.
Gates
| name | test-conventions |
| description | PPDS test conventions — which test framework to use per area, trait categories, file placement, coverage bar. Use when writing or organizing tests across .NET, TypeScript, or MCP code. |
Where each kind of test lives, which framework it uses, and how to label it.
| Area | Test Type | Trait / Framework | Notes |
|---|---|---|---|
| Application Services | Unit (mocked deps) | Unit | Mock IDataverseConnectionPool, IProgressReporter |
| Dataverse SDK logic | FakeXrmEasy | Unit | Use FakeXrmEasyTestsBase for SDK behavior |
| Query engine | Unit (pure functions) | Unit | Deterministic transforms |
| Import orchestration | Unit + FakeXrmEasy | Unit | Mock pool, bulk executor |
| CLI commands | Unit (mock services) | Unit | Commands are thin wrappers — test services |
| TUI extracted logic | Unit | TuiUnit | Business logic, not Terminal.Gui rendering |
| Extension panels | Vitest | N/A | Message contracts + handler behavior |
| MCP tools | Unit (mock services) | Unit | Param validation + basic execution |
| Live Dataverse | Integration | Integration | Needs test-dataverse environment |
Mirror the source path under tests/:
src/PPDS.Cli/Services/AuthService.cs
tests/PPDS.Cli.Tests/Services/AuthServiceTests.cs
Project naming: {SourceProject}.Tests (unit) or {SourceProject}.IntegrationTests
(integration / live). Class naming: {ClassUnderTest}Tests.
80% on new code (patch coverage), enforced by Codecov on PRs. Aim higher in new modules; the bar is a minimum, not a target.
Every spec acceptance criterion (AC-NN) must have a corresponding test —
this is Constitution principle I6. Tag the test with [Trait("AC", "AC-NN")]
so the AC-coverage script can verify completeness.
# Fast unit suite (no external deps, ~30s)
dotnet test PPDS.sln --filter "Category!=Integration" -v q
# TUI unit tests only
dotnet test --filter "Category=TuiUnit"
# Live Dataverse integration (requires test environment)
dotnet test PPDS.sln --filter "Category=Integration" -v q
# Extension unit (Vitest)
npm run ext:test
# Extension end-to-end (Playwright Electron)
npm run ext:test:e2e
# TUI snapshot suite (Node, captures terminal frames)
npm run tui:test
Test conventions are situational — they only matter when authoring tests. Loading them into every session would crowd out genuinely-global context. The skill auto-loads when you reach for tests; outside that context, it sits idle.
See docs/CLAUDE-MD-GOVERNANCE.md for the routing rationale.