mstest

Filter MSTest results to show pass/fail and errors in .NET projects.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jacobrocks1212/claude-config --skill mstest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mstest
Source: https://github.com/jacobrocks1212/claude-config/tree/main/repos/cognito-forms/.claude/skills/mstest
Command: npx skills add https://github.com/jacobrocks1212/claude-config --skill mstest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates filtering of MSTest results to display only passed, failed, and error outputs, reducing noise during test runs.

Core Features & Use Cases

  • Filter tests by ClassName, Name, or TestDll to quickly target Cognito.UnitTests or Cognito.Forms.UnitTests.
  • Run all tests or filtered subsets with a deterministic script using test-filtered.ps1.
  • Integrate with CI or local development to streamline test feedback.

Quick Start

Run the tests with the mstest command, optionally using -Filter and -TestDll to target Cognito.UnitTests or Cognito.Forms.UnitTests.

Frequently Asked Questions about mstest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I filter MSTest results to show only pass/fail outcomes in .NET CI pipelines?

Filter MSTest results by invoking the test-filtered.ps1 PowerShell script, which reduces output noise by displaying only passed, failed, and error results for targeted .NET test DLLs.

Can I run specific Cognito.UnitTests or Cognito.Forms.UnitTests without executing the entire test suite?

You can run specific Cognito.UnitTests by passing the -Filter and -TestDll parameters to the mstest command, targeting tests by ClassName, Name, or TestDll for deterministic subsets.

What is the best way to consistently reproduce MSTest runs across local development and CI environments?

The best way to reproduce MSTest runs consistently is using a deterministic test-filtered.ps1 script with MSTest command flags, ensuring identical test execution behavior across local and CI environments.

Why does my MSTest output have too much noise during backend test runs?

MSTest output contains noise because standard runs include verbose diagnostic information; applying test-filtered.ps1 filters the output to show only pass/fail results and errors, streamlining feedback.

Does the MSTest filtering script work with PowerShell on any .NET project?

The filtering script works with .NET projects using MSTest, specifically targeting Cognito.UnitTests or Cognito.Forms.UnitTests through PowerShell invocation of test-filtered.ps1 in CI or local environments.