Systematic JUnit 5 patterns for testing numeric limits, null/empty cases, and edge conditions.
Works with
Covers numeric boundaries (Integer.MIN_VALUE, MAX_VALUE, zero), string edge cases (null, empty, whitespace), and collection sizes (empty, single, many)
Includes parameterized test examples using @ParameterizedTest and @ValueSource for efficient multi-case coverage
Demonstrates floating-point precision testing with tolerance-based assertions, overflow/underflow detection, and special values
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionunit-test-boundary-conditionsExecute the skills CLI command in your project's root directory to begin installation:
Fetches unit-test-boundary-conditions from giuseppe-trisciuoglio/developer-kit and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate unit-test-boundary-conditions. Access via /unit-test-boundary-conditions in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
194
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
194
stars
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.
@ParameterizedTest with @ValueSource or @CsvSource for multiple boundary valuesisCloseTo(expected, within(tolerance)) with AssertJMath.addExact() and Math.subtractExact() to detect arithmetic overflowRequires: junit-jupiter, junit-jupiter-params, assertj-core.
import org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.ValueSource;
import static org.assertj.core.api.Assertions.*;
class IntegerBoundaryTest {
@ParameterizedTest
@ValueSource(ints = {Integer.MIN_VALUE, Integer.MIN_VALUE + 1, 0, Integer.MAX_VALUE - 1, Integer.MAX_VALUE})
void shouldHandleIntegerBoundaries(int value) {
assertThat(value).isNotNull();
}
@Test
void shouldDetectIntegerOverflow() {
assertThatThrownBy(() -> Math.addExact(Integer.MAX_VALUE, 1))
.isInstanceOf(ArithmeticException.class);
}
@Test
void shouldDetectIntegerUnderflow() {
assertThatThrownBy(() -> Math.subtractExact(Integer.MIN_VALUE, 1))
.isInstanceOf(ArithmeticException.class);
}
@Test
void shouldHandleZeroEdge() {
int result = MathUtils.divide(0, 5);
assertThat(result).isZero();
assertThatThrownBy(() -> MathUtils.divide(5, 0))
.isInstanceOf(ArithmeticException.class);
}
}
import org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.ValueSource;
class StringBoundaryTest {
@ParameterizedTest
@ValueSource(strings = {"", " ", " ", "\t", "\n"})
void shouldRejectEmptyAndWhitespace(String input) {
boolean result = StringUtils.isNotBlank(input);
assertThat(result).isFalse();
}
@Test
void shouldHandleNullString() {
String result = StringUtils.trim(null);
assertThat(result).isNull();
}
@Test
void shouldHandleSingleCharacter() {
assertThat(StringUtils.capitalize("a")).isEqualTo("A");
assertThat(StringUtils.trim("x")).isEqualTo("x");
}
@Test
void shouldHandleVeryLongString() {
String longString = "x".repeat(1000000);
assertThat(longString.length()).isEqualTo(1000000);
assertThat(StringUtils.isNotBlank(longString)).isTrue();
}
}
class CollectionBoundaryTest {
@Test
void shouldHandleEmptyList() {
List<String> empty = List.of();
assertThat(empty).isEmpty();
assertThat(CollectionUtils.first(empty)).isNull();
assertThat(CollectionUtils.count(empty)).isZero();
}
@Test
void shouldHandleSingleElementList() {
List<String> single = List.of("only");
assertThat(single).hasSize(1);
assertThat(CollectionUtils.first(singleImplementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
tailwind-css-patterns
20giuseppe-trisciuoglio/developer-kit
Frontendsame reponextjs-code-review
8giuseppe-trisciuoglio/developer-kit
Frontendsame repodrizzle-orm-patterns
7giuseppe-trisciuoglio/developer-kit
Productivitysame reponestjs-best-practices
7giuseppe-trisciuoglio/developer-kit
Productivitysame repograalvm-native-image
4giuseppe-trisciuoglio/developer-kit
Productivitysame repotest-cases
21cexll/myclaude
Testingtag: testReviews
4.7★★★★★57 reviews- KKabir Kapoor★★★★★Dec 28, 2024
unit-test-boundary-conditions is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- DDhruvi Jain★★★★★Dec 24, 2024
I recommend unit-test-boundary-conditions for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- MMichael Desai★★★★★Dec 4, 2024
unit-test-boundary-conditions reduced setup friction for our internal harness; good balance of opinion and flexibility.
- KKabir Desai★★★★★Dec 4, 2024
Useful defaults in unit-test-boundary-conditions — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- NNaina Farah★★★★★Nov 23, 2024
unit-test-boundary-conditions is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- KKabir Wang★★★★★Nov 23, 2024
I recommend unit-test-boundary-conditions for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- KKofi Taylor★★★★★Nov 19, 2024
unit-test-boundary-conditions reduced setup friction for our internal harness; good balance of opinion and flexibility.
- OOshnikdeep★★★★★Nov 15, 2024
Useful defaults in unit-test-boundary-conditions — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- KKaira Abebe★★★★★Oct 14, 2024
Useful defaults in unit-test-boundary-conditions — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- KKofi Reddy★★★★★Oct 14, 2024
unit-test-boundary-conditions reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 57
1 / 6Discussion
Comments — not star reviews- No comments yet — start the thread.