java-unit-test SKILL.md skillA

java-unit-test from baixuanzhu/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add baixuanzhu/skills/java-unit-test@v2.0.0

Pins v2.0.0 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

baixuanzhu/skills

Path

eval/java-test/darwin-validation-v2.0.0/snapshots/blind/unit-B/versionA/SKILL.md

Versions recorded

1

Latest version

v2.0.0, committed Oct 4, 2026

Size

11,833 bytes

Repository stars

3

License

MIT

Java 开发期测试（纯单元测试）助手——@Mock + @InjectMocks，毫秒级，不起 Spring Context、不起容器、零测试基础设施。在编写、评审、补全、重构单元 测试时使用本技能，无论用户是否提到具体框架（unit test / JUnit / Mockito / 测试用例 / 怎么测 / 测哪些 / 写多少）。 次级触发信号——代码或 pom 中出现：spring-boot-starter-test、junit-jupiter、 @Test / @BeforeEach / @ParameterizedTest / @MethodSource、 assertEquals / assertThrows / assertThat / extracting（AssertJ）、 @Mock / @InjectMocks / MockitoAnnotations.openMocks、mockStatic / MockedStatic、mockito-core； 用户任务词或痛点出现：只写 happy path、补测试不知道写几个、手写一堆重复…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Java 开发期测试

开发期测试 = **纯单元测试**：`@Mock`+`@InjectMocks`，毫秒级，`mvn test` 秒级跑完——不起 Spring Context、不引 Testcontainers / H2，零测试基础设施。规范分两部分——**A. 设计方法**（等价类/边界值/决策表/状态迁移）保证测得全；**B. 工程默认值与纪律**（断言库/Mock 边界/停止标准）保证每次一样。每条规则含「✗ 错误设计 → ✓ 正确设计」。

> 接口级验证（"接口通不通"）不写测试、不属本技能范围；需要真实依赖断言 / 可重复回归的重型测试 → java-integration-test，明示或确认后激活。

## 三条铁律

1. **设计优先于编码**：先确定"测哪些用例"（等价类/边界值/决策表/状态），再落成 `@Test`。禁止上来就写代码、想到哪测到哪——那是"覆盖率的幻觉"，不是测试设计。
2. **最小充分集**：用等价类合并代表"无穷输入"，用边界值钉住 off-by-one 高发区；穷尽测试不可能，目标是"用最少的用例覆盖最有代表性的输入"。一个方法的有效用例通常在 3~8 个之间。
3. **零基础设施**：纯单测不起 Spring、不引 Testcontainers / H2 / 内嵌库。需要真实依赖才能断言的行为（SQL 实际执行 / 迁移 / 缓存语义）不属单测——→ java-integration-test（激活后）。

## 断言库策略

**默认用 JUnit 原生 `Assertions`（`assertEquals`/`assertThrows`/`assertTrue` 等）。仅当满足以下任一条件时，升级到 AssertJ：**

- **集合内容断言**（断言 list 元素构成/顺序/提取字段）—— AssertJ 的 `containsExactlyInAnyOrder` / `extracting(...)`。
- **字段分组断言**（同一逻辑组的多个字段作为一个整体校验，如坐标 x/y/z、时间窗 start/end）—— AssertJ 的 `extracting(...).containsExactly(...)`。

**其余场景（简单值、抛异常、各列语义独立的逐列断言如表格型 VO）一律 JUnit 原生，不切换。升级标准可机械执行：是否集合？是否同一逻辑组？两条都不是 → 留在原生逐列断言（失败定位准、加列只改一处）。**

- Spring 项目 `spring-boot-starter-test` 已传递 AssertJ，触发条件时直接用；非 Spring 项目首次触发时按 `references/03` §1 引入 `assertj-core`。
…

Read the whole file at its exact version.

How to install

mdr add baixuanzhu/skills/java-unit-test@sha256:e823b8b500a32b6a

[![mdr](https://markdownregistry.com/badge/art_4rmiuqgvvof3ifpf.svg)](https://markdownregistry.com/a/art_4rmiuqgvvof3ifpf)

Versions

The registry has recorded 1 version of this file, committed on Oct 4, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_4rmiuqgvvof3ifpf
GET https://markdownregistry.com/api/v1/resolve?ref=baixuanzhu/skills/java-unit-test
GET https://markdownregistry.com/api/v1/blob/e823b8b500a32b6a6e74c18853bccdc918249ffb56072f333d69b599a69a0539

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from baixuanzhu/skills

Every file in baixuanzhu/skills

Other files named java-unit-test

Browse by kind, by grade A, or by owner.