claude

dotnet-test-creator

Polyglot unit-test generation via an orchestrated Research → Plan → Implement → Validate agent pipeline, with deep .NET test-framework skills (MSTest/TUnit authoring, migrations, CRAP scores).

1 on GitHubupdated 7 days ago
/

Plugin dotnet-test-creator from marketplace kiro-starter-kit in dwalleck/kiro-starter-kit. Commands read from the repo's manifest — 6 days ago.

What it installs

Skills (28)

  • assertion-quality

    Analyzes the variety and depth of assertions across test suites in any language. Use when the user asks to evaluate assertion quality, find shallow testing, identify assertion-free tests (no assertions or only trivial ones like Assert.IsNotNull / expect(x).toBeTruthy() / assert x is not None), flag

  • code-testing-agent-ide

    Generates and writes new unit tests for any programming language using a Research-Plan-Implement-Validate pipeline, orchestrated by the main agent through IDE subagents. Use when asked to generate tests, write unit tests, add tests, improve test coverage, create test project, achieve high coverage,

  • code-testing-agent

    Generates and writes new unit tests for any programming language using a Research-Plan-Implement pipeline. Use when asked to generate tests, write unit tests, add tests, improve test coverage, create test project, achieve high coverage, comprehensive tests, or asked to scaffold a new test project fo

  • code-testing-extensions

    Provides file paths to language-specific extension files for the code-testing pipeline. Call this skill to discover available extension guidance files (e.g., dotnet.md for .NET, cpp.md for C++). Do not use directly — invoked by code-testing agents and skills that need language-specific references.

  • coverage-analysis

    Project-wide code coverage and CRAP (Change Risk Anti-Patterns) score analysis for .NET projects. Calculates CRAP scores per method and surfaces risk hotspots — complex code with low coverage that is dangerous to modify. Use to diagnose why coverage is stuck or plateaued, identify what methods block

  • crap-score

    Calculates targeted CRAP (Change Risk Anti-Patterns) scores for a named .NET method, class, or single source file. Use when the user explicitly asks to compute CRAP scores or assess risky untested code for a specific target, combining Cobertura coverage data with cyclomatic complexity analysis. DO N

  • detect-static-dependencies

    Scan C# source files for hard-to-test static dependencies — DateTime.Now/UtcNow, File.*, Directory.*, Environment.*, HttpClient, Console.*, Process.*, and other untestable statics. Produces a ranked report of static call sites by frequency. USE FOR: find untestable statics, scan for static dependenc

  • dotnet-test-frameworks

    Reference data for .NET test framework detection patterns, assertion APIs, skip annotations, setup/teardown methods, and common test smell indicators across MSTest, xUnit, NUnit, and TUnit. Loaded by test analysis skills (test-anti-patterns) as framework-specific lookup tables.

  • filter-syntax

    Reference data for test filter syntax across all platform and framework combinations: VSTest --filter expressions, MTP filters for MSTest/NUnit/xUnit v3/TUnit, and VSTest-to-MTP filter translation. DO NOT USE directly — loaded by run-tests, mtp-hot-reload, and migrate-vstest-to-mtp when they need fi

  • generate-testability-wrappers

    Generate wrapper interfaces and DI registration for hard-to-test static dependencies in C#. Produces IFileSystem, IEnvironmentProvider, IConsole, IProcessRunner wrappers, or guides adoption of TimeProvider and IHttpClientFactory. USE FOR: generate wrapper for static, create IFileSystem wrapper, wrap

  • migrate-mstest-v1v2-to-v3

    Migrate MSTest v1 or v2 test project to MSTest v3. Use when user says "upgrade MSTest", "upgrade to MSTest v3", "migrate to MSTest v3", "update test framework", "modernize tests", "MSTest v3 migration", "MSTest compatibility", "MSTest v2 to v3", or build errors after updating MSTest packages from 1.

  • migrate-mstest-v3-to-v4

    Fix build errors and breaking changes after upgrading MSTest from v3 to v4, or plan a complete MSTest v3-to-v4 migration. Use when user says "upgrade to MSTest v4", "MSTest 4 migration", "MSTest v4 breaking changes", "tests don't compile after upgrading MSTest", or has errors CS0507, CS0103, CS1061,

  • migrate-static-to-wrapper

    Mechanically replace static dependency call sites with wrapper or built-in abstraction calls across a bounded scope (file, project, or namespace). Performs codemod-style bulk replacement of DateTime.UtcNow to TimeProvider.GetUtcNow(), File.ReadAllText to IFileSystem, and similar transformations. Add

  • migrate-to-tunit

    Migrate xUnit, NUnit, or MSTest test suites to TUnit. Use whenever the user wants to port tests from another framework to TUnit, or asks how to convert specific patterns: [Fact]/[Theory]/[InlineData]/IClassFixture (xUnit), [TestCase]/[TestCaseSource]/[SetUp]/[OneTimeSetUp] (NUnit), [TestClass]/[Test

  • migrate-vstest-to-mtp

    Migrates .NET test projects from VSTest to Microsoft.Testing.Platform (MTP). Use when user asks to "migrate to MTP", "switch from VSTest", "enable Microsoft.Testing.Platform", "use MTP runner", or mentions EnableMSTestRunner, EnableNUnitRunner, or UseMicrosoftTestingPlatformRunner. USE FOR: MTP beha

  • migrate-xunit-to-xunit-v3

    Migrates .NET test projects from xUnit.net v2 to xUnit.net v3. USE FOR: upgrading xunit to xunit.v3. DO NOT USE FOR: migrating between test frameworks (MSTest/NUnit to xUnit.net), migrating from VSTest to Microsoft.Testing.Platform (use migrate-vstest-to-mtp). For xUnit v3 MTP filter syntax (--filte

  • mtp-hot-reload

    Suggests using Microsoft Testing Platform (MTP) hot reload to iterate fixes on failing tests without rebuilding. Use when user says "hot reload tests", "iterate on test fix", "run tests without rebuilding", "speed up test loop", "fix test faster", or needs to set up MTP hot reload to rapidly iterate

  • platform-detection

    Reference data for detecting the test platform (VSTest vs Microsoft.Testing.Platform) and test framework (MSTest, xUnit, NUnit, TUnit) from project files. DO NOT USE directly — loaded by run-tests, mtp-hot-reload, and migrate-vstest-to-mtp when they need detection logic.

  • run-tests

    For `dotnet test`: figures out which test platform (VSTest vs Microsoft.Testing.Platform) a project uses from `Directory.Build.props`, `global.json`, and `.csproj`, then picks the matching command syntax. USE FOR: running, filtering, or troubleshooting `dotnet test`; identifying the test runner/plat

  • test-analysis-extensions

    Provides file paths to language-specific reference files for the test ANALYSIS skills (assertion-quality, test-anti-patterns, test-gap-analysis, test-smell-detection, test-tagging). Call this skill to discover available extension files (e.g., dotnet.md for .NET/MSTest/xUnit/NUnit/TUnit, python.md fo

  • test-anti-patterns

    Audits existing test code in any language for anti-patterns and quality issues — produces a severity-ranked report (Critical / Warning / Info) with concrete code-level fixes. Polyglot: .NET (MSTest/xUnit/NUnit/ TUnit), Python (pytest/unittest), TS/JS (Jest/Vitest/Mocha/node:test), Java (JUnit/TestNG

  • test-gap-analysis

    Performs pseudo-mutation analysis on production code in any language to find gaps in existing test suites. Use when the user asks to find weak tests, discover untested edge cases, check if tests would catch a bug, or evaluate test effectiveness through mutation-style reasoning. Analyzes production c

  • test-smell-detection

    Deep-dive audit using the full testsmells.org 19-smell academic catalog for tests in any language. Every finding maps to a named, citable smell from the research literature (Assertion Roulette, Duplicate Assert, Mystery Guest, Eager Test, Sensitive Equality, Conditional Test Logic, Sleepy Test, Magi

  • test-tagging

    Analyzes test suites in any language and tags each test with a standardized set of traits (positive, negative, critical-path, boundary, smoke, regression, integration, performance, security). Use when the user wants to categorize, audit, or label tests with traits. Works with .NET (MSTest TestCatego

  • tunit-aot-compatibility

    Make TUnit test projects work under NativeAOT, IL trimming, and single-file publishing. Use when the user is publishing a TUnit test project with PublishAot=true, hits TUnit0058 errors about generic tests, sees IL2026/IL3050 trim warnings on test data sources, asks about [GenerateGenericTest], or ne

  • tunit-mocking

    TUnit's source-generated, AOT-compatible mocking framework — TUnit.Mocks. Use whenever the user is mocking dependencies in TUnit tests, references Mock.Of<T>(), `.Mock()` extension methods, `Any()`, `Is<T>(...)`, `WasCalled(Times.Once)`, or asks how to stub HttpClient/ILogger/ILogger<T> in TUnit. Al

  • writing-mstest-tests

    Write new MSTest unit tests and implement concrete fixes in existing MSTest code using MSTest 3.x/4.x modern APIs and best practices. USE FOR: write unit tests for a class, write MSTest tests, create test class, fix test assertions, MSTest assertion APIs (StartsWith, EndsWith, MatchesRegex, IsGreate

  • writing-tunit-tests

    Best practices for writing TUnit unit and integration tests. Use whenever the user is writing, fixing, reviewing, or modernizing TUnit tests, or asks about [Test], [Arguments], [Before(Test)]/[After(Test)], [MethodDataSource], [ClassDataSource], [MatrixDataSource], hooks, lifecycle, parallelism, tim

Subagents (4)

  • code-testing-implementer-ide

    Stage 3 of the IDE code-testing pipeline. Implements the test plan — writes test files and runs build/test/fix INLINE via shell. On a fix re-run, only addresses the gaps named in the validator's feedback. Never modifies production code. Appends per-phase results to .testagent/status.md. Launched in

  • code-testing-planner-ide

    Stage 2 of the IDE code-testing pipeline. Reads .testagent/research.md and writes a phased .testagent/plan.md assigning every in-scope source file to a leaf-first phase with concrete test cases. Does not write tests, run commands, or modify source. Launched in sequence by the orchestrator (code-test

  • code-testing-researcher-ide

    Stage 1 of the IDE code-testing pipeline. Analyzes a codebase for test generation and writes .testagent/research.md (language, framework, build/test commands, in-scope files, API surface, existing coverage). Does not write tests or modify source. Launched in sequence by the orchestrator (code-testin

  • code-testing-validator-ide

    Stage 4 of the IDE code-testing pipeline. Runs a full non-incremental build + full test run + coverage-gap check + a test-quality audit (test-gap-analysis, assertion-quality, test-anti-patterns), then reports a verdict. Returns NEEDS_WORK + categorized FAILING/MISSING/WEAK/SMELL feedback when issues

View source on GitHub

More from dwalleck/kiro-starter-kit

All 6 plugins →

Polyglot unit-test generation as a Kiro workflow (kiro-cli 2.26.0+, KAS engine) built on the current dotnet-test plugin: test-engineer entry agent, then Research → Plan → repeat[Implement, Validate] gated on a verdict file, handing off through .git/testagent/ so nothing is ever stageable. Ships the vendored dotnet-test skills.

11 skills · 6 agents

1

Max-effort, recall-mode code review as a Kiro workflow for native Windows with no Python: eight parallel finder angles, per-candidate verification, a gap sweep, re-votes on unstable verdicts, then ranked findings and postable Conventional Comments.

4 agents

1

Builds features via an engine-enforced Spec → Probe → Design → Plan → Build → Validate pipeline that refuses to advance on a vague spec or disproven understanding, and loops when built code drifts from the plan.

1

Orchestrated PR code review agents for the Kiro CLI: an orchestrator plus six specialists (code-reviewer, code-simplifier, comment-analyzer, pr-test-analyzer, silent-failure-hunter, type-design-analyzer).

1

Orchestrated PR code review agents for the Kiro CLI: an orchestrator plus six specialists (code-reviewer, code-simplifier, comment-analyzer, pr-test-analyzer, silent-failure-hunter, type-design-analyzer).

1

Maintain dotnet-test-creator?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins6 plugins