Audit a test file or suite; produce a severity-ranked diagnostic report. ALWAYS USE for tests that verify nothing, missing/tautological assertions, swallowed/broad exceptions, flaky/order-dependent tests, duplication, or magic values. Polyglot. DO NOT USE for direct edits: writing-mstest-tests owns supplied MSTest assertions/attributes/lifecycle; code-testing owns new tests. Exclude running tests, migration, assertion metrics (assertion-quality), raw .NET coverage collection (run-tests), non-.NE
Install
KitScout test notes
Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.
Similar tools
rea-analysis-optimization456,653 ★ Optimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserv
rea-ci-tests-audit456,653 ★ Audit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for s
diagnosing-bugs323,485 ★ Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or r
migrate-to-shoehorn323,485 ★ Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, w
webapp-testing193,970 ★ Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend