ワンクリックでManusで任意のスキルを実行

java-junit

スター0

フォーク0

更新日2026年5月5日 20:43

JUnit 5 testing best practices for this Java Spring Boot backend. Use when adding or reviewing backend tests, Mockito tests, parameterized tests, Spring Boot test slices, integration tests, or Maven test commands.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

DevExpGbb

DevExpGbb/ghcp-architecture-n-more

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

JUnit 5 Best Practices

Source: adapted from github/awesome-copilot skill java-junit and this repository's Spring Boot testing conventions.

When to Use

Adding tests under backend/src/test/java
Refactoring Java code and deciding what tests should move with it
Writing controller, service, repository, or configuration tests
Introducing parameterized tests or Mockito-based unit tests

Procedure

Inspect backend/pom.xml to confirm the available JUnit, Spring Boot Test, Mockito, AssertJ, and testcontainers dependencies.
Place tests under backend/src/test/java mirroring the production package where practical.
Prefer the narrowest useful test type:
- Plain JUnit + Mockito for service logic
- @WebMvcTest for controller behavior
- @DataJpaTest for repository behavior when JPA exists
- @SpringBootTest only when full context wiring is part of the behavior under test
Use Arrange-Act-Assert structure and descriptive test names such as methodName_shouldExpectedBehavior_whenScenario.
Keep tests independent and deterministic. Do not rely on execution order unless the test is explicitly documenting order-sensitive behavior.
Use @ParameterizedTest with @ValueSource, @CsvSource, @EnumSource, or @MethodSource when the same behavior needs multiple inputs.
Prefer AssertJ fluent assertions when available; otherwise use JUnit assertions with clear failure messages.
Mock external collaborators, not value objects. Verify observable outcomes before implementation details.
For Azure integrations, keep local unit tests credential-free. Integration tests should use test doubles or explicitly documented test resources.
Run tests from backend with mvn test when Maven is available.

Review Checklist

Test name describes behavior and scenario
Test has one clear reason to fail
Mocks are used only at service boundaries
Parameterized tests avoid copy-pasted cases
Spring test scope is no broader than needed
No test requires real Azure credentials by default

このリポジトリの他の Skills

同じリポジトリ

azure-pricing

DevExpGbb/ghcp-architecture-n-more

Azure retail pricing and cost estimate workflow. Use when estimating Azure service costs, comparing SKUs or regions, building dev/uat/prd cost tables, pricing Azure Container Apps, PostgreSQL, Redis, Service Bus, Event Hubs, Storage, Key Vault, Log Analytics, or validating Azure monthly cost assumptions.

2026-05-070

az-cost-optimize

DevExpGbb/ghcp-architecture-n-more

Azure cost optimization workflow for Terraform IaC and deployed resources. Use when analyzing Azure spend, reducing costs, finding right-sizing opportunities, comparing dev/uat/prd environments, or creating cost optimization recommendations for Container Apps, PostgreSQL, Redis, Service Bus, Event Hubs, Storage, Key Vault, and Log Analytics.

2026-05-050

azure-terraform-best-practices

DevExpGbb/ghcp-architecture-n-more

Azure Terraform best practices and deployment preflight workflow. Use when creating, editing, reviewing, validating, or planning infra/**/*.tf, azurerm resources, tfvars environments, Azure Container Apps infrastructure, managed identity, Key Vault, networking, observability, or Terraform deployment readiness.

2026-05-050

java-docs

DevExpGbb/ghcp-architecture-n-more

Javadoc and Java API documentation guidance. Use when documenting public Java types, controllers, service contracts, records, exceptions, or non-obvious backend behavior in backend/**/*.java.

2026-05-050

java-springboot

DevExpGbb/ghcp-architecture-n-more

Spring Boot best practices for Java 21 backend work. Use when creating, reviewing, refactoring, or testing backend/**/*.java, Spring Boot controllers/services/configuration, REST APIs, external clients, resilience, logging, validation, or Flyway-backed persistence in this repository.

2026-05-050

terraform-azurerm-set-diff-analyzer

DevExpGbb/ghcp-architecture-n-more

Analyze Terraform plan JSON output for AzureRM Provider Set-type attributes and distinguish false-positive order-only diffs from actual resource changes. Use when reviewing Terraform plans for Azure Application Gateway, Load Balancer, Firewall, Front Door, Network Security Group, route table, virtual network, private endpoint, or other azurerm resources with noisy nested block diffs.

2026-05-050

JUnit 5 Best Practices

Source: adapted from github/awesome-copilot skill java-junit and this repository's Spring Boot testing conventions.

When to Use

Adding tests under backend/src/test/java

Refactoring Java code and deciding what tests should move with it

Writing controller, service, repository, or configuration tests

Introducing parameterized tests or Mockito-based unit tests

Procedure

Inspect backend/pom.xml to confirm the available JUnit, Spring Boot Test, Mockito, AssertJ, and testcontainers dependencies.

Place tests under backend/src/test/java mirroring the production package where practical.

Prefer the narrowest useful test type:

Plain JUnit + Mockito for service logic
@WebMvcTest for controller behavior
@DataJpaTest for repository behavior when JPA exists
@SpringBootTest only when full context wiring is part of the behavior under test

Use Arrange-Act-Assert structure and descriptive test names such as methodName_shouldExpectedBehavior_whenScenario.

Keep tests independent and deterministic. Do not rely on execution order unless the test is explicitly documenting order-sensitive behavior.

Use @ParameterizedTest with @ValueSource, @CsvSource, @EnumSource, or @MethodSource when the same behavior needs multiple inputs.

Prefer AssertJ fluent assertions when available; otherwise use JUnit assertions with clear failure messages.

Mock external collaborators, not value objects. Verify observable outcomes before implementation details.

For Azure integrations, keep local unit tests credential-free. Integration tests should use test doubles or explicitly documented test resources.

Run tests from backend with mvn test when Maven is available.

Review Checklist

Test name describes behavior and scenario

Test has one clear reason to fail

Mocks are used only at service boundaries

Parameterized tests avoid copy-pasted cases

Spring test scope is no broader than needed

No test requires real Azure credentials by default

name	java-junit
description	JUnit 5 testing best practices for this Java Spring Boot backend. Use when adding or reviewing backend tests, Mockito tests, parameterized tests, Spring Boot test slices, integration tests, or Maven test commands.