Why extensions customize JUnit behavior - Quick Recap

Recall & Review

beginner

What is the main purpose of extensions in JUnit?

Extensions in JUnit allow you to add or change how tests run, like setting up extra steps before or after tests, without changing the test code itself.

beginner

How do JUnit extensions help with test setup and cleanup?

They let you run code before and after tests automatically, so you don’t have to repeat setup or cleanup code in every test.

intermediate

Name one example of behavior that can be customized using JUnit extensions.

You can customize how tests handle exceptions, how test results are reported, or add custom conditions to skip tests.

intermediate

Why is it better to use extensions instead of changing test code directly?

Using extensions keeps test code clean and focused on testing logic, while extensions handle extra tasks separately, making tests easier to read and maintain.

beginner

What is a real-life example of using a JUnit extension?

Imagine you want to take a screenshot every time a test fails. Instead of adding code in every test, you use an extension that does this automatically.

What do JUnit extensions mainly allow you to do?

A Automatically fix bugs in your code

B Change how tests run without modifying test code

C Write tests faster by skipping assertions

D Generate test data randomly

Extensions let you add or change test behavior without changing the test code itself.

Which of these is a common use of JUnit extensions?

A Changing the programming language of tests

B Encrypting test results

C Compiling code faster

D Running setup code before tests

Extensions often run setup or cleanup code automatically around tests.

Why should you use extensions instead of adding setup code in every test?

A To keep tests clean and avoid repeating code

B Because extensions run tests faster

C To avoid writing assertions

D Because extensions replace test frameworks

Extensions help keep test code simple by handling repeated tasks separately.

Which behavior can NOT be customized by JUnit extensions?

A Changing the Java version used to run tests

B Skipping tests under certain conditions

C Modifying test result reporting

D Handling exceptions during tests

JUnit extensions cannot change the Java version; they customize test behavior only.

What is an example of a task automated by a JUnit extension?

A Changing test method names

B Writing new test cases automatically

C Taking screenshots on test failure

D Fixing code bugs during tests

Extensions can automate tasks like taking screenshots when tests fail.

Explain why JUnit extensions are useful for customizing test behavior.

Think about how extensions help avoid repeating code.

Describe a real-life scenario where using a JUnit extension improves testing.

Consider tasks done on test failure or before tests.

Practice

1. What is the main reason to use extensions in JUnit tests?

easy

A. To add extra behavior without changing the test code

B. To write test cases faster

C. To replace the JUnit framework

D. To create user interfaces for tests

Solution

1. Step 1: Understand the purpose of extensions

   Extensions allow adding extra behavior like setup or cleanup without modifying test methods.

2. Step 2: Compare options with this purpose

   Only To add extra behavior without changing the test code matches this purpose; others describe unrelated goals.

3. Final Answer:

   To add extra behavior without changing the test code -> Option A

4. Quick Check:

   Extensions add behavior = D [OK]

Hint: Extensions add behavior without changing tests [OK]

Common Mistakes:

• Thinking extensions speed up writing tests
• Confusing extensions with replacing JUnit
• Assuming extensions create UI

2. Which annotation is used to apply an extension to a JUnit test class or method?

easy

A. @TestExtension

B. @UseExtension

C. @ExtendWith

D. @EnableExtension

Solution

1. Step 1: Recall the correct annotation for extensions

   The standard JUnit annotation to apply extensions is @ExtendWith.

2. Step 2: Verify other options

   Other options are not valid JUnit annotations for extensions.

3. Final Answer:

   @ExtendWith -> Option C

4. Quick Check:

   @ExtendWith = C [OK]

Hint: Remember '@ExtendWith' applies extensions [OK]

Common Mistakes:

• Using @TestExtension which does not exist
• Confusing with @UseExtension or @EnableExtension
• Forgetting the '@' symbol

3. Given this code snippet, what will be printed when the test runs?

@ExtendWith(MyExtension.class)
class MyTest {
  @Test
  void testMethod() {
    System.out.println("Test running");
  }
}

Assuming MyExtension prints "Before test" before the test and "After test" after the test.

medium

A. Test running\nBefore test\nAfter test

B. Before test\nTest running\nAfter test

C. After test\nTest running\nBefore test

D. Test running only

Solution

1. Step 1: Understand extension behavior

   MyExtension runs code before and after the test method, printing "Before test" and "After test" respectively.

2. Step 2: Order of output

   Output order is: before test message, test method message, after test message.

3. Final Answer:

   Before test\nTest running\nAfter test -> Option B

4. Quick Check:

   Extension runs before/after test = A [OK]

Hint: Extensions run code before and after tests [OK]

Common Mistakes:

• Assuming extension runs after test only
• Mixing order of printed lines
• Ignoring extension output

4. Identify the error in this JUnit test using an extension:

@ExtendWith(MyExtension.class)
class TestClass {
  @Test
  void test() {
    System.out.println("Running test");
  }

  void helper() {
    System.out.println("Helper method");
  }
}

Why might helper() not be called during test execution?

medium

A. Extension disables helper methods

B. Helper method must be private

C. Helper method must be static

D. Helper method is not annotated with @Test

Solution

1. Step 1: Check method annotations

   Only methods annotated with @Test run as tests; helper() lacks this annotation.

2. Step 2: Understand extension role

   Extensions do not disable helper methods; they only affect test lifecycle.

3. Final Answer:

   Helper method is not annotated with @Test -> Option D

4. Quick Check:

   Missing @Test means no run = B [OK]

Hint: Only @Test methods run automatically [OK]

Common Mistakes:

• Thinking extensions disable helper methods
• Believing helper must be static or private
• Assuming all methods run as tests

5. You want to create a JUnit extension that changes test data before each test runs. Which approach best uses extensions to achieve this?

hard

A. Implement BeforeEachCallback and modify test data in beforeEach()

B. Override the test method and change data inside it

C. Use @Test annotation with parameters to change data

D. Create a separate test class for each data variation

Solution

1. Step 1: Identify extension interface for pre-test actions

   The BeforeEachCallback interface allows running code before each test method.

2. Step 2: Apply this to modify test data

   Modifying test data in beforeEach() method is the correct way to customize data before tests.

3. Final Answer:

   Implement BeforeEachCallback and modify test data in beforeEach() -> Option A

4. Quick Check:

   BeforeEachCallback modifies data before tests = A [OK]

Hint: Use BeforeEachCallback to run code before tests [OK]

Common Mistakes:

• Trying to override test methods directly
• Misusing @Test parameters for data changes
• Creating many classes instead of using extensions