java-integration-test SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
java-integration-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-integration-test@v2.3.0Pins v2.3.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- baixuanzhu/skills
- Path
plugins/java-test/skills/java-integration-test/SKILL.md- Versions recorded
- 5
- Latest version
- v2.3.0, committed Oct 24, 2026
- First version recorded
- Oct 24, 2026
- Size
- 11,909 bytes
- Repository stars
- 3
- License
- MIT
Java/Spring Boot 集成测试助手——测试自管真实依赖：真实关系库 / 缓存 / 消息队列 （PostgreSQL、MySQL、Redis、Kafka 等）、迁移可重放、事务传播真实效果、冒烟、 API 级 E2E、外部调用隔离、契约切片层（@WebMvcTest / @JsonTest / @RestClientTest）。 三个决策按序：① 建不建（这段代码的回归由谁值守——有专职测试就不自建，个人/ 小团队自动化是唯一回归网）② 放哪层（断言离开真实依赖还成立吗）③ 用什么跑 （Docker → Testcontainers / 本地实库 + 独立 schema / 都没有 → 能验的用同族嵌入式 替身验、不能验的列清单移交真库）。 Testcontainers 是首选执行方式不是技能定义；降级必须写明走哪条与环境盲区， 不许静默拿替身当生产方言。仅当需求明确需要这一层时使用：用户明示（"补集成 测试 / 需求冻结 / 准备发版"）→ 直接开始；仅能推断 → 先问一句；无信号 → 不写， 新功能测试 → java-unit-test。…
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 集成测试（真实依赖 / 冒烟 / E2E） 本技能管**测试自己拉起并管理真实依赖**的那一层：真实数据库与中间件、迁移可重放、事务传播的实际效果、冒烟、API 级 E2E、外部调用隔离。与开发期测试的分界沿**依赖轴**——开发期零外部基础设施（→ java-unit-test），本层自己起依赖，CI 无预置环境也能重复跑。 **Testcontainers 是首选执行方式，不是本层定义。** 它属回归阶段，开发阶段要的是毫秒级反馈。没有 Docker 时本层仍有合法路径，见决策 ③。 > 判据与陷阱围绕 **Spring 的测试上下文**（`@SpringBootTest` / 切片注解 / `@MockitoBean` / Testcontainers）。换 Micronaut / Quarkus / 纯 JUnit 自建容器，三个决策照旧成立，下面的陷阱表基本归零——它们不是「测试」的通用坑，是 Spring 测试容器特有的欺骗方式。 ## 三个决策，按序走完 顺序不能换：先判该不该建，再判放哪层，最后才判用什么跑。跳过 ① 直接问"怎么起容器"，等于假定这一层一定要有。 ### ① 建不建 —— 这段代码的回归由谁值守 | 值守情况 | 动作 | |---|---| | 有专职测试 / QA | 不自建，开发只保证单测绿；用户明示要才写 | | 无专职测试（个人 / 小团队） | 建，但优先**冒烟 + 核心链路**，不铺分支矩阵 | | 判断不了 | 先问"这个模块的回归谁跑"，再决定 | 不自建不是偷懒——专职同学的用例会长期维护，你写的那份下次需求变更就烂在那。 > ① 只决定**集成层**建不建。契约切片（`@WebMvcTest` / `@JsonTest` / `@RestClientTest`）秒级、不碰真实依赖，不受 ① 排除——有专职测试也照写。 **激活时机**（与上表叠加）： | 信号 | 动作 | |---|---| | **明示**：用户说"补集成测试 / 需求冻结 / 准备发版 / 要 Testcontainers" | 直接开始，不追问 | | **推断**：特性已稳 + SQL 密集 + 覆盖为零，用户没说 | 先问一句，确认后动手 | | **无信号**：开发期常规写码 / 新功能开发 | 不新增；新测试 → java-unit-test；存量照跑照修 | > 这一层是十秒级/条的重资产，写在还变动的行为上 = 需求每变一次连带重写。默认永远从轻，重的东西等人开口。 ### ② 放哪层 —— 这条断言离开真实依赖还成立吗 …
Read the whole file at its exact version.
How to install
mdr add baixuanzhu/skills/java-integration-test@sha256:c0501671d541f861The line at the top of this page pins the label v2.3.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_u5pqhvphnw2yicaz)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, all committed on Oct 24, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.3.0 latest | 2026-10-24 | 95aa2f2 | 11,909 B | A | view · diff |
| v2.2.0 | 2026-10-24 | a217e9f | 10,727 B | A | view · diff |
| v2.2.0 | 2026-10-24 | c34a109 | 9,990 B | A | view · diff |
| v2.2.0 | 2026-10-24 | 8ee193f | 9,803 B | A | view · diff |
| v2.2.0 | 2026-10-24 | d3663e1 | 10,635 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11909 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
baixuanzhu/skills · 3 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_u5pqhvphnw2yicaz GET https://markdownregistry.com/api/v1/resolve?ref=baixuanzhu/skills/java-integration-test GET https://markdownregistry.com/api/v1/blob/c0501671d541f861ea2506ffd7724b10cb471254be26a7640626f37fa443e361
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