@EnabledIfEnvironmentVariable in JUnit - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding @EnabledIfEnvironmentVariable Usage

What is the primary purpose of the JUnit annotation @EnabledIfEnvironmentVariable?

A To enable a test only when a system property is set

B To disable a test permanently regardless of environment variables

C To run a test only if a specific environment variable matches a given value

D To run a test only if the JVM version is above a certain number

💡 Hint

Think about controlling test execution based on environment settings.

The annotation @EnabledIfEnvironmentVariable allows tests to run conditionally based on the value of an environment variable. It checks if the variable matches the specified value before enabling the test.

❓ Predict Output

intermediate

Test Execution Result with @EnabledIfEnvironmentVariable

Given the following test code, what will be the test execution result if the environment variable TEST_MODE is set to production?

JUnit

import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.condition.EnabledIfEnvironmentVariable;

public class EnvVarTest {

    @Test
    @EnabledIfEnvironmentVariable(named = "TEST_MODE", matches = "development")
    void testOnlyInDevelopment() {
        System.out.println("Running test in development mode");
    }
}

A Test will run but not print anything

B Test will be skipped (disabled) because TEST_MODE is 'production'

C Test will fail with an exception due to environment variable mismatch

D Test will run and print the message

💡 Hint

Check the value the annotation expects versus the actual environment variable.

The test is enabled only if TEST_MODE equals development. Since it is production, the test is skipped.

❓ assertion

advanced

Correct Assertion for Environment Variable Check

Which assertion correctly verifies that a test method annotated with @EnabledIfEnvironmentVariable(named = "MODE", matches = "test") runs only when the environment variable MODE is set to test?

A assertTrue(System.getenv("MODE").equals("test"))

B assertEquals("test", System.getProperty("MODE"))

C assertNotNull(System.getenv("MODE"))

D assertFalse(System.getenv("MODE").isEmpty())

💡 Hint

Remember environment variables are accessed differently than system properties.

Environment variables are accessed via System.getenv(). The assertion checks if the variable MODE equals test, matching the annotation condition.

🔧 Debug

advanced

Debugging @EnabledIfEnvironmentVariable Not Working

A developer writes a test with @EnabledIfEnvironmentVariable(named = "APP_ENV", matches = "staging") but the test is skipped even when APP_ENV is set to staging. What is the most likely cause?

A The environment variable <code>APP_ENV</code> is not set in the test runtime environment

B The annotation <code>@EnabledIfEnvironmentVariable</code> does not support the <code>matches</code> attribute

C The test method is missing the <code>@Test</code> annotation

D JUnit version does not support conditional annotations

💡 Hint

Consider how environment variables are passed to the test process.

If the environment variable is missing, the condition defaults to false and the test is skipped. The developer should ensure the variable is set in the environment where tests run.

❓ framework

expert

Combining @EnabledIfEnvironmentVariable with Other Conditions

Consider a test annotated with both @EnabledIfEnvironmentVariable(named = "REGION", matches = "US") and @EnabledIfEnvironmentVariable(named = "VERSION", matches = "1.0"). Under which condition will the test run?

A The test will never run because multiple @EnabledIfEnvironmentVariable annotations are not supported

B If either REGION equals 'US' or VERSION equals '1.0'

C Only if REGION equals 'US', VERSION is ignored

D Only if both REGION equals 'US' and VERSION equals '1.0'

💡 Hint

Think about how multiple conditional annotations combine in JUnit.

Multiple @EnabledIfEnvironmentVariable annotations combine with logical AND, so all conditions must be true for the test to run.