10 Plugins aus öffentlichen Claude Code marketplaces. Jedes bündelt Skills, Slash-Commands, Agents, Hooks oder MCP servers, die zusammen installiert werden.
Zeige 10 Plugins, die diesen Filtern entsprechen.
Reiche das repo mit .claude-plugin/marketplace.json ein und wir listen jedes plugin auf.
Marketplace einreichenTest reporting and coverage analytics: JUnit XML, LCOV and Cobertura parsing, Allure reports, coverage diffs, and test run summaries for pull requests. Also covers JaCoCo and coverage.py analysis, risk-ranked coverage targets, TestRail / Xray / Zephyr Scale result sync, and Currents analytics. Agents (daily-test-suite-aggregator, release-quality-report-agent) roll up daily results across suites and assemble a release-quality go / no-go report. Jest and Vitest coverage lives in qa-unit-tests-js.
foundationsPython unit testing with pytest: fixtures, parametrize, markers, mocking, coverage and CI, plus async tests with pytest-asyncio. Covers framework choice and test conventions, with unittest and doctest as references.
functional-testingGo and Rust unit testing: table-driven Go tests with t.Run subtests, benchmarks, native fuzzing and the race detector, plus cargo test with Criterion. Each language skill covers framework choice and test conventions, with Ginkgo and Go mocking, rstest and mockall as references.
functional-testingGenerate high-quality unit tests. Analyzes code, prints a Given-When-Then test case list, then writes the tests and verifies they compile and pass. Java support covers JUnit 5, Mockito, and AssertJ.
JavaScript and TypeScript unit testing with Jest and Vitest: configuration, mocking, coverage, CI, and choosing between the two. References cover Mocha maintenance, Jasmine-to-Jest migration, and deep coverage analysis. Test-code hygiene lives in qa-test-review.
functional-testingJVM unit testing with JUnit 5: parameterized tests, lifecycle hooks, extensions, coverage and CI, plus framework choice for Java, Kotlin, Groovy and Scala. References cover Kotest, Spock, TestNG, ScalaTest and AssertJ.
functional-testing.NET unit testing with xUnit.net: Fact and Theory tests, fixtures, parallel execution and CI, with NUnit, MSTest and FluentAssertions as references. Recommends xUnit for new projects, follows an existing NUnit or MSTest convention, and notes the FluentAssertions v8 license change.
functional-testingUse when you need to write unit tests for Spring Boot applications — including pure unit tests with @ExtendWith(MockitoExtension.class) for @Service/@Component, slice tests with @WebMvcTest and @MockitoBean for controllers, @JsonTest for JSON serialization, parameterized tests with @CsvSource/@MethodSource, test profiles, and @TestConfiguration. For framework-agnostic Java use @131-java-testing-unit-testing. For integration tests use @322-frameworks-spring-boot-testing-integration-tests.
Use when you need to write fast unit tests for Quarkus applications — including pure tests with @ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock for full CDI mock replacement, @InjectSpy for partial CDI bean mocking, REST Assured for resource-focused tests, @ParameterizedTest with @CsvSource / @MethodSource, QuarkusTestProfile for test-specific configuration overrides, and naming conventions (*Test → Surefire, *IT → Failsafe). For framework-agnostic Java use @131-java-testing-unit-testing.
Use when you need to write unit tests for Micronaut applications — Mockito-first with @ExtendWith(MockitoExtension.class), @MicronautTest with @MockBean, HttpClient @Client("/") assertions, @Property overrides, @ParameterizedTest, and *Test vs *IT naming. For framework-agnostic Java use @131-java-testing-unit-testing.
