unit-test-boundary-conditions SKILL.md skillA
unit-test-boundary-conditions from giuseppe-trisciuoglio/developer-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add giuseppe-trisciuoglio/developer-kit/unit-test-boundary-conditions@git:20260324.a02e282Pins git:20260324.a02e282 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- giuseppe-trisciuoglio/developer-kit
- Path
plugins/developer-kit-java/skills/unit-test-boundary-conditions/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260324.a02e282, committed Mar 24, 2026
- First version recorded
- Feb 7, 2026
- Size
- 9,005 bytes
- Repository stars
- 367
- License
- MIT
Provides edge case, corner case, boundary condition, and limit testing patterns for Java unit tests. Validates minimum/maximum values, null cases, empty collections, numeric overflow/underflow, floating-point precision, and off-by-one scenarios using JUnit 5 and AssertJ. Use when writing .java test files to ensure code handles limits, corner cases, and special inputs correctly.
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
# Unit Testing Boundary Conditions and Edge Cases ## Overview Systematic patterns for testing boundary conditions, corner cases, and limit values in Java using JUnit 5. Covers numeric boundaries, string edge cases, collection states, floating-point precision, date/time limits, and off-by-one scenarios. ## When to Use - Numeric min/max limits, null/empty/whitespace inputs - Overflow/underflow validation, collection boundaries - Off-by-one errors, floating-point precision ## Instructions 1. **Identify boundaries**: List numeric limits (MIN_VALUE, MAX_VALUE, zero), string states (null, empty, whitespace), collection sizes (0, 1, many) 2. **Apply parameterized tests**: Use `@ParameterizedTest` with `@ValueSource` or `@CsvSource` for multiple boundary values 3. **Test both sides of boundaries**: Cover values just below, at, and just above each boundary 4. **Run tests after adding each boundary category** to catch issues early 5. **Verify floating-point precision**: Use `isCloseTo(expected, within(tolerance))` with AssertJ 6. **Test collection states**: Explicitly test empty (0), single (1), and many (>1) element scenarios …
Read the whole file at its exact version.
How to install
mdr add giuseppe-trisciuoglio/developer-kit/unit-test-boundary-conditions@sha256:ac324f6bc2d86013The line at the top of this page pins the label git:20260324.a02e282, 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_uiycrc36efkydrp7)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Feb 7, 2026 and Mar 24, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260324.a02e282 latest | 2026-03-24 | a02e282 | 9,005 B | A | view · diff |
| git:20260316.91dc3c4 | 2026-03-16 | 91dc3c4 | 13,553 B | A | view · diff |
| git:20260223.c6d4db1 | 2026-02-23 | c6d4db1 | 13,549 B | A | view · diff |
| v1.0.1 | 2026-02-08 | 147afce | 13,648 B | A | view · diff |
| v1.0.1 | 2026-02-07 | 654d94d | 11,768 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 (9005 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
giuseppe-trisciuoglio/developer-kit · 367 stars · license MIT · pushed 2026-09-10 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uiycrc36efkydrp7 GET https://markdownregistry.com/api/v1/resolve?ref=giuseppe-trisciuoglio/developer-kit/unit-test-boundary-conditions GET https://markdownregistry.com/api/v1/blob/ac324f6bc2d860135c0175c71c114b1c6c5b730e73054394580dfd5233e1714b
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.