การทดสอบแบบมีเงื่อนไขและสมมติฐาน

Some tests only make sense on a particular OS, JRE, or when a service is available. Running them everywhere causes false failures.

JUnit 5 offers conditional execution and assumptions to handle this gracefully.

The simplest control is @Disabled, which skips a test entirely. Always include a reason so the team knows why.

Use @EnabledOnOs or @DisabledOnOs to run a test only on certain platforms, perfect for filesystem or path tests.

@EnabledOnJre and @EnabledForJreRange gate tests by Java version, useful when a feature only exists on newer runtimes.

Run a test only when an environment variable matches, ideal for tests that need a specific deployment context.

Similarly, @EnabledIfSystemProperty gates a test on a JVM system property, letting you toggle suites from the command line.

For complex logic, @EnabledIf points to a method returning a boolean. The test runs only if it returns true.

Conditional annotations decide before a test starts. Assumptions decide partway through: if an assumption fails, the test is aborted (skipped), not failed.

assumeTrue aborts the test when a runtime condition is not met, so the rest of the assertions never run and the test is marked skipped.

assumingThat runs a block of assertions only if a condition holds, while the rest of the test always executes.

Use conditions wisely:

• Prefer annotations for static conditions known upfront
• Use assumptions for runtime checks
• Always give @Disabled a reason
• Avoid over-skipping, which hides real coverage gaps

Test your conditional execution knowledge.

You controlled when tests run:

• @Disabled skips; OS, JRE, env, and property annotations gate tests
• @EnabledIf handles custom conditions
• Assumptions abort (skip) tests at runtime, not fail them
• assumingThat runs partial assertions conditionally

Conditional execution keeps your suite green across diverse environments.