Does this skill support JUnit 5 features?

Yes, it fully supports JUnit 5, including advanced features like @Nested test classes, while ensuring they still follow the required Maven naming conventions.

How does it prevent unit tests from running during the integration phase?

It configures the integration-tests profile to automatically set skipTests to true for the Surefire plugin while enabling the Failsafe plugin for integration tests.

Why use this skill instead of standard JUnit configurations?

This skill specifically manages the integration layer, separating it from unit tests using the Failsafe plugin to ensure faster builds and cleaner CI/CD pipelines by avoiding redundant test execution.

What naming conventions are required for this skill to work?

The skill enforces the standard Maven patterns of *IT.java or *ITCase.java to ensure the Failsafe plugin correctly identifies integration tests vs unit tests.

JUnit Integration Testing for Maven

Name: JUnit Integration Testing for Maven
Author: cuioss

bycuioss

Seguridad y Pruebas

Standardizes Maven integration testing by configuring the Failsafe plugin, naming conventions, and dedicated build profiles.

Acerca de

This skill provides a comprehensive framework for managing integration tests within Maven-based Java projects. It enforces the critical separation of fast-running unit tests from more complex integration tests by configuring the Maven Failsafe plugin, establishing strict naming conventions (e.g., *IT.java), and defining dedicated Maven profiles. By implementing these standards, it ensures reliable CI/CD pipelines where integration tests run independently and only when required, preventing build bloat and improving developer feedback loops.

Características Principales

Standardized naming conventions for integration test classes
Automatic Maven Failsafe plugin configuration and goal mapping
Dedicated 'integration-tests' Maven profile generation
0 GitHub stars
Smart unit test exclusion logic to prevent redundant test execution
Pre-configured CI/CD workflow patterns for GitHub Actions

Casos de Uso

Separating long-running database or API tests from rapid unit test suites
Standardizing testing patterns across a multi-module Maven microservice architecture
Configuring CI/CD pipelines to run integration tests only on specific branches or triggers

Acerca de

Características Principales

Standardized naming conventions for integration test classes
Automatic Maven Failsafe plugin configuration and goal mapping
Dedicated 'integration-tests' Maven profile generation
0 GitHub stars
Smart unit test exclusion logic to prevent redundant test execution
Pre-configured CI/CD workflow patterns for GitHub Actions

Casos de Uso

Separating long-running database or API tests from rapid unit test suites
Standardizing testing patterns across a multi-module Maven microservice architecture
Configuring CI/CD pipelines to run integration tests only on specific branches or triggers