testing-java

Java testing with JUnit 5 and Mockito: test lifecycle, mocking, and integration test patterns

1.14x

Quality

63%

Does it follow best practices?

Impact

92%

1.14x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/testing-java/SKILL.md

Evaluation results

100%

30%

Inventory Service: Unit Tests with Mocking

Unit tests with Mockito mocking patterns

Criteria

Without context

With context

MockitoExtension annotation

100%

@Mock annotation used

100%

No Mockito.mock() calls

100%

@InjectMocks used

100%

verify() used

100%

@Captor used

100%

Test method naming

100%

Arrange comment

100%

Act & Assert comment

100%

@Test annotation

100%

77%

Price Formatter: Parameterized Validation Tests

Parameterized tests for edge-case coverage

Criteria

Without context

With context

@ParameterizedTest annotation

100%

Input source annotation

100%

Multiple whitespace variants

100%

JUnit 5 @Test annotation

100%

Test method naming

58%

Arrange comment

Act & Assert comment

@ExtendWith(MockitoExtension) if mocks present

100%

No Mockito.mock() calls

100%

User Registration Service: Integration Test Setup

Integration test setup with JaCoCo coverage

Criteria

Without context

With context

@SpringBootTest or @DataJpaTest

100%

H2 in-memory database

100%

H2 dependency scope

100%

Integration test source set

100%

Separate Gradle task for integration tests

100%

JaCoCo plugin applied

100%

jacocoTestReport task

100%

jacocoTestCoverageVerification task

100%

80% coverage minimum

100%

No Mockito.mock() in integration test

100%

Repository: ucdavis/ai-skills-registry
Commit: c0b2e4b

Evaluated: about 15 hours ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Inventory Service: Unit Tests with Mocking Price Formatter: Parameterized Validation Tests User Registration Service: Integration Test Setup

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.