testfx-test-value-evidence
Apply the vendored test-value-evidence skill with TestFx toolchain, assertion, parallel-safety, packed-consumer, and review conventions. Use when implementing or reviewing behavior-changing TestFx PRs or commits, including source-only changes.
- License 许可
- MIT
- 所属仓库
- microsoft/testfx
- 最近更新
- 2026-11-14
- Stars
- ★ 1.1k
- Forks
- 315
01 前言 Front Matter
- name
- testfx-test-value-evidence
- description
- Apply the vendored test-value-evidence skill with TestFx toolchain, assertion, parallel-safety, packed-consumer, and review conventions. Use when implementing or reviewing behavior-changing TestFx PRs or commits, including source-only changes.
03 SKILL.md 正文
TestFx test-value evidence
Read and apply the canonical test-value-evidence skill first, then these repository-specific requirements. Keep the canonical vendored file unmodified; its source revision and blob are recorded in eng/vendored-files.json.
- Read repository instructions. Use the
repository-pinned toolchain through
build.cmdorbuild.sh, capture binary logs for MSBuild commands, and use the owning project's assertion conventions andBannedSymbols.txt. MSTest framework tests useTestContainer; MTP and analyzer tests use MSTest; adapter tests use their established assertion APIs. - Apply parallel-safety preflight before test/lifecycle changes and against the final diff. Counterfactual experiments must use isolated outputs and preserve the actual test scheduling.
- For acceptance, package, launcher, protocol, or cross-component changes, apply acceptance validation. Repack each product variant before testing, prove the effective package/cache and loaded binary paths, and retain real shipping-layout evidence. Assert/API overload changes also need the repository's packed source-compatibility coverage.
- Reuse the installed test-gap-analysis for bounded static reasoning and the existing mutation workflow for available executed Stryker evidence. Do not upgrade unrelated curated plugins to run this skill.
- Keep publication under the code-review gate.
The automatic and
/review-testsreviewers are read-only: report static predictions or unavailable proof unless exact matching execution records can be inspected. Do not execute PR code or infer red-green proof from green CI. Put material evidence gaps in the summary, not automatic inline findings.
The existing review workflow reports the canonical evidence table for each eligible PR head, including unchanged tests protecting source-only changes. Individual commit validation is separate; neither the skill nor its vendored presence enforces a Git hook or proves live workflow publication.
04 同仓库更多 Skills
dotnet-breaking-changes
Use before changing .NET/C# code whose callers you do not control: a NuGet library, or a repo with PublicAPI.Shipped/Unshipped.txt, ApiCompat, multiple TargetFrameworks, InternalsVisibleTo, or generated (.g.cs) partials. Green builds miss silent breaks from optional parameters, parameter names, sealing, const values, nullability, and #if. USE FOR: "without breaking existing callers"; adding a public method, overload, optional parameter, or interface member to a shipped library; renaming a public method or an internal helper a friend assembly uses; consolidating duplicated logic; changing a signature, nullability, default, or attribute; adding a target framework; RS0016/RS0017 or ApiCompat errors; "is this PR breaking?". For a rename, extract, or merge, also invoke csharp-refactoring. DO NOT USE FOR: an executable whose callers all live in one project; renaming a local variable or private member, even in a shipped library; formatting; framework/SDK/NuGet upgrades (use dotnet-upgrade).
testfx-parallel-safety-preflight
Check concurrency and isolation before implementing or refactoring TestFx tests, lifecycle code, helpers, shared-state declarations, or production paths those tests exercise. Use before narrowing DoNotParallelize or ResourceLock, changing parallelization settings, or introducing asynchronous workers; repeat against the final diff.
testfx-localization-validation
Validate generated TestFx localization catalogs, resource IDs, placeholders and locked tokens. Use for RESX/XLF changes, OneLoc PRs, localization build failures, duplicate targets or units, and orphaned translation entries.
testfx-acceptance-validation
Validate TestFx shipping paths and capable CI execution using packed consumers, package/cache provenance, exact exits and artifacts, and selected-versus-executed test evidence. Use for acceptance regressions, package/MSBuild/launcher/protocol changes, or skipped-only CI results; not for unrelated unit-only or documentation changes.
session-delivery-hygiene
Gate local-session scope, persistent delivery, live PR state, integration provenance, and owned cleanup. Use before implementing guidance changes, changing or pushing PR work, diagnosing package/output mismatches, or handing off implementation.
post-release-activities
Systematic activities that need to be performed after a release is done.