Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/joshsmithxrm/power-platform-developer-suite/test-conventionsnpx skills add joshsmithxrm/power-platform-developer-suite --skill test-conventionsgit clone --depth 1 https://github.com/joshsmithxrm/power-platform-developer-suiteWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/test-conventions)<a href="https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/test-conventions"><img src="https://agentmods.dev/badge/skills/joshsmithxrm/power-platform-developer-suite/test-conventions.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00043 | $0.00727 |
| Opus 5 | $0.00022 | $0.00364 |
| Sonnet 5 | $0.00009 | $0.00145 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
test-conventions scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Conventions
Where each kind of test lives, which framework it uses, and how to label it.
When to Use
- Writing a new test class
- Deciding "should this be a unit test or a FakeXrmEasy test?"
- Looking up where to put a test file
- Adding the right trait so CI filters work
Conventions Table
| 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 |
File Placement
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.
Coverage Bar
80% on new code (patch coverage), enforced by Codecov on PRs. Aim higher in new modules; the bar is a minimum, not a target.
AC Mapping
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.
Running Tests
# 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
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 84 lines · 43 tokens per session scan A 776e9d1503d2
test-conventions is a skill published in the GitHub repository joshsmithxrm/power-platform-developer-suite (7 stars, last pushed 5d ago), licensed MIT. It adds 43 tokens to every session and 727 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
dynamics365-expert
Expert in Dynamics 365 platform, model-driven apps, canvas apps, Power Automate flows, Dataverse, plugins, and custom workflows. Use when the user mentions Microsoft platforms, ERP, CRM, business apps, the Power Platform, or Dataverse, or when the task involves Dynamics 365 Applications, Dataverse Platform…
PowerAppsControl
Drive the PowerAppsControl MCP server to UX-test a Power App end to end: open and verify an app URL, let the user choose a mode (smoke test = in-depth read-only exploration that produces a repeatable natural-language test plan; or run my test plan), then run it in a recorded session and produce a video + HTML report…
xrm-mcp
Skip steps you already have answers for. If you ran listtables or describetable earlier in the session, reuse those results.
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…