testfx-test-value-evidence

$npx mdskill add microsoft/testfx/testfx-test-value-evidence

Read and apply the canonical [test-value-evidence skill](../../../.agents/skills/test-value-evidence/SKILL.md) first, then these repository-specific requirements. Keep the canonical vendored file unmodified; its source revision and blob are recorded in [eng/vendored-files.json](../../../eng/vendored-files.json).

SKILL.md

.github/skills/testfx-test-value-evidenceView on GitHub ↗
---
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.
---

# TestFx test-value evidence

Read and apply the canonical
[test-value-evidence skill](../../../.agents/skills/test-value-evidence/SKILL.md)
first, then these repository-specific requirements. Keep the canonical vendored
file unmodified; its source revision and blob are recorded in
[eng/vendored-files.json](../../../eng/vendored-files.json).

- Read [repository instructions](../../copilot-instructions.md). Use the
  repository-pinned toolchain through `build.cmd` or `build.sh`, capture binary
  logs for MSBuild commands, and use the owning project's assertion conventions
  and `BannedSymbols.txt`. MSTest framework tests use `TestContainer`; MTP and
  analyzer tests use MSTest; adapter tests use their established assertion APIs.
- Apply [parallel-safety preflight](../testfx-parallel-safety-preflight/SKILL.md)
  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](../testfx-acceptance-validation/SKILL.md). 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](../../../.agents/skills/test-gap-analysis/SKILL.md) for
  bounded static reasoning and the existing
  [mutation workflow](../../workflows/mutation-testing.yml) for available
  executed Stryker evidence. Do not upgrade unrelated curated plugins to run
  this skill.
- Keep publication under the [code-review gate](../code-review/SKILL.md).
  The automatic and `/review-tests` reviewers 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.

More from microsoft/testfx

SkillDescription
assertion-qualityAnalyze assertion quality, depth, variety, and false confidence in existing tests. ALWAYS USE when asked about weak, shallow, trivial, always-true, self-referential, assertion-free, presence/truthiness-only, or insufficiently diverse assertions, including MSTest, Jest, pytest, and Go. DO NOT USE for direct fixes: writing-mstest-tests owns supplied MSTest assertions; code-testing owns new cases. Use test-gap-analysis when asked whether tests would catch a production change, and test-anti-patterns for general severity-ranked audits.
behavior-preserving-refactorPreserve observable behavior when splitting files, moving members, consolidating helpers, or simplifying TestFx code. Use for structural refactors and file-diet implementation; inventory baseline semantics and consumers, then run focused equivalence checks.
binlog-failure-analysisDiagnose existing MSBuild .binlog failures with MCP/replay; not log capture or non-MSBuild failures.
binlog-generationCapture and verify unique MSBuild binlogs, quoting '-bl:{}' in PowerShell; not analysis of existing logs.
build-parallelismAnalyze an MSBuild solution, solution filter, or Build.proj that schedules multiple project files. USE FOR: measured idle worker nodes, `-m` that does not scale, a serial ProjectReference critical path, graph builds, or an MSBuild task that builds a Projects list. Requires at least two distinct project files whose scheduling or throughput must be analyzed. DO NOT USE for non-MSBuild build systems.
build-perf-baselineMeasure repeatable cold/changed-input/no-op MSBuild baselines for caching, output layout and graph tuning; not task diagnosis or non-MSBuild builds.
build-perf-diagnosticsDiagnose MSBuild target/task/analyzer bottlenecks from binlogs after baselining; not baseline setup, incremental correctness or parallelism tuning.
check-bin-obj-clashDetects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, or missing/overwritten outputs in multi-project or multi-targeting builds where bin/obj (or project.assets.json) collide. Common causes: shared OutputPath, missing AppendTargetFrameworkToOutputPath, extra global properties (e.g. PublishReadyToRun), or SetTargetFramework on a ProjectReference to a single-targeting project. DO NOT USE FOR: file access errors unrelated to MSBuild (OS-level locking), single-project single-TFM builds, non-MSBuild build systems.
code-testing>-
code-testing-agent>-