test-tagging

Classifies existing tests by standard traits and reports their distribution. USE FOR: tagging all tests with category attributes, categorizing/tagging/ labeling each test, compare happy vs error paths, audit the test mix, describe coverage shape by test type, or tag then verify the project builds. Read bodies when names mislead. Apply canonical attributes; otherwise report only. DO NOT USE FOR: requests owned by test-anti-patterns, coverage-analysis, crap-score, test-gap-analysis, code-testing,

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-optimization 456,653 ★
  Optimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserv
• rea-ci-tests-audit 456,653 ★
  Audit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for s
• diagnosing-bugs 323,485 ★
  Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or r
• migrate-to-shoehorn 323,485 ★
  Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, w
• webapp-testing 193,970 ★
  Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend