agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/VSSDK-Analyzers/.agents/skills/testing/SKILL.md

testing

Skill56 starsChanged 4 months agoMITView on GitHub

Provides guidance and instructions for writing, running and filtering tests.

194 other projects use a version of this, 6 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use assign-copilot, build-and-dependency and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • zetaloopSkill

    assign-copilot

    Assigns a GitHub issue to the Copilot coding agent, optionally specifying a custom agent. Use this when asked to assign an issue to Copilot or delegate an issue to CCA.

    Also in 3 projects that use this

  • NVIDIA-NeMoSkill

    build-and-dependency

    Dev environment setup for Megatron Bridge — container-based development, uv package management, lockfile regeneration, adding dependencies, Slurm container usage, and common build pitfalls.

    Also in 3 projects that use this

  • timmo001Skill

    changeset-scope

    Keep all scoped code work contained to the user-defined changeset. Use for implementation, fixes, diagnosis, refactoring, cleanup, and review when explicit instructions, named files, diffs, branches, pull requests, or injected work scopes define the boundary.

    Also in 3 projects that use this

  • JetBrainsSkill

    module-dependencies

    Add or modify IntelliJ module dependencies in `.iml` files.

    Also in 3 projects that use this

  • CES-LtdSkill

    oss-pr

    Use when creating a pull request, after committing changes, or when user invokes /oss-pr. Covers branch management, quality checks, commit, push, and PR creation.

    Also in 3 projects that use this

  • CES-LtdSkill

    pr-automation

    PR Automation Orchestrator: poll open PRs, check CI, run review, fix, and merge eligible PRs. Use when: (1) Invoked by daemon via scripts/pr-automation.sh, (2) User says "/pr-automation".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 174 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use --treenode-filter to select tests by assembly, namespace, class, method, or property

    line 62

“Common” is measured: kept by at least 6 in 10 of the 174 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

IMPORTANT: This repository uses TUnit with Microsoft.Testing.Platform (MTP v2). Traditional --filter syntax does NOT work. Use the options below instead.

  • There should generally be one test project (under the test directory) per shipping project (under the src directory). Test projects are named after the project being tested with a .Tests suffix.
  • Tests use TUnit with Microsoft.Testing.Platform (MTP v2), while retaining xUnit assertions. Traditional VSTest --filter syntax does NOT work.

Running Tests

There may be unstable tests that are attributed as such. Running the dotnet-test-cloud.ps1 script will execute all previously built tests except the unstable ones. The commands below will not automatically exclude unstable tests, but you may do so by adding a parameter to filter out those that set their TestCategory property to FailsInCloudTest.

Run all tests (from the root of the repository):

dotnet test --no-build -c Release

To run a specific test project, change to that project's directory first; the commands below then target it without hard-coding its path.

Run tests for a specific test project (within that test project's directory):

dotnet test --no-build -c Release

Run a single test method:

dotnet test --no-build -c Release -- --treenode-filter "/*/*/ClassName/MethodName"

Run all tests in a test class:

dotnet test --no-build -c Release -- --treenode-filter "/*/*/ClassName/*"

Run tests with wildcard matching (supports wildcards at beginning and/or end):

dotnet test --no-build -c Release -- --treenode-filter "/*/*/*/*Pattern*"

Run tests with a specific property:

dotnet test --no-build -c Release -- --treenode-filter "/*/*/*/*[PropertyName=value]"

Run tests for a specific framework only:

dotnet test --no-build -c Release --framework net472

List all available tests without running them:

dotnet run --no-build -c Release --framework net472 -- --list-tests

Key points about test filtering with TUnit / MTP v2:

  • Options after -- are passed to the test runner, not to dotnet test
  • Use --treenode-filter to select tests by assembly, namespace, class, method, or property
  • Traditional VSTest --filter expressions do NOT work
  • Wildcards * are supported in tree node segments
  • See --help for query filter language for advanced scenarios

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free