Please enable JavaScript.

Coggle requires JavaScript to display documents.

Junit - Coggle Diagram

- - - - public class LoggingExtension implements TestInstancePostProcessor { @Override public void postProcessTestInstance(Object testInstance, ExtensionContext context) throws Exception { Logger logger = LogManager.getLogger(testInstance.getClass()); testInstance.getClass() .getMethod("setLogger", Logger.class) .invoke(testInstance, logger); } }
      - This type of extension is executed after an instance of a test has been created. A typical use case for this extension is injecting dependencies into the instance
    - - public class EnvironmentExtension implements ExecutionCondition { @Override public ConditionEvaluationResult evaluateExecutionCondition( ExtensionContext context) { Properties props = new Properties(); props.load(EnvironmentExtension.class .getResourceAsStream("application.properties")); String env = props.getProperty("env"); if ("qa".equalsIgnoreCase(env)) { return ConditionEvaluationResult .disabled("Test disabled on QA environment"); } return ConditionEvaluationResult.enabled( "Test enabled on QA environment"); } }
      - If we do not want a condition to be validated, we can deactivate it by setting the junit.conditions.deactivate configuration key to a pattern that matches the condition.
    - - This set of extensions is related to events in a test's lifecycle and can be defined by implementing the following interfaces:
        
        BeforeAllCallback and AfterAllCallback – executed before and after all the test methods are executed
        
        BeforeEachCallBack and AfterEachCallback – executed before and after each test method
        
        BeforeTestExecutionCallback and AfterTestExecutionCallback – executed immediately before and immediately after a test method
      - If the test also defines its lifecycle methods, the order of execution is:
        BeforeAllCallback
        BeforeAll
        BeforeEachCallback
        BeforeEach
        BeforeTestExecutionCallback
        Test
        AfterTestExecutionCallback
        AfterEach
        AfterEachCallback
        AfterAll
        AfterAllCallback
    - - If a test constructor or method receives a parameter, this must be resolved at runtime by a ParameterResolver.
    - - Last but not least, the TestExecutionExceptionHandler interface can be used to define the behavior of a test when encountering certain types of exceptions.
      - public class IgnoreFileNotFoundExceptionExtension implements TestExecutionExceptionHandler { Logger logger = LogManager .getLogger(IgnoreFileNotFoundExceptionExtension.class); @Override public void handleTestExecutionException(ExtensionContext context, Throwable throwable) throws Throwable { if (throwable instanceof FileNotFoundException) { logger.error("File not found:" + throwable.getMessage()); return; } throw throwable; } }