Spring Test

Question 1

What is the difference between unit and integration testing?

Answer 1

Unit testing is the testing of the smallest units of code in isolation. Dependencies are often mocked

Integration testing is the testing of units of code working together. Dependencies are rarely mocked

Question 2

True or False

The Spring TestContext creates an ApplicationContext for your tests

Answer 2

True

Question 3

True or False

The Spring TestContext caches an ApplicationContext between @Test methods by default

Answer 3

True

Question 4

What is a test suite?

Answer 4

In the context of Spring, a test suite is a test class

Question 5

True or False

The TestContext rolls back a transaction for each @Test method by default

Answer 5

True

Question 6

What bean must be defined in the test’s ApplicationContext to provide transactional support?

Answer 6

PlatformTransactionManager

Question 7

Which annotation can be used to persist database transactions performed by @Test methods?

Answer 7

@Commit

Question 8

Which annotation can be used to specify a properties resource location for test classes?

Answer 8

@TestPropertySource

Question 9

Which annotation can be used to create a new ApplicationContext after a @Test method executes?

Answer 9

@DirtiesContext

Question 10

True or False

Although field injection is discouraged in production code, field injection is actually quite natural in test code

Answer 10

True

The rationale for the difference is that you will never instantiate your test class directly

Question 11

Method-level lifecycle methods — for example, methods annotated with JUnit Jupiter’s @BeforeEach or @AfterEach — are run within a test-managed transaction. On the other hand, suite-level and class-level lifecycle methods — for example, methods annotated with JUnit Jupiter’s @BeforeAll or @AfterAll and methods annotated with TestNG’s @BeforeSuite, @AfterSuite, @BeforeClass, or @AfterClass — are not run within a test-managed transaction.

Question 12

@BeforeTransaction and @AfterTransaction

Question 13

@SpringJUnitConfig(TestConfig.class)
class OrderServiceIntegrationTests {

@RepeatedTest(10)
void placeOrderRepeatedly(RepetitionInfo repetitionInfo,
		@Autowired OrderService orderService) {

	// use orderService from the test's ApplicationContext
	// and repetitionInfo from JUnit Jupiter
} }

Question 14

Which annotation can be used to repeat an arbitrary amount of test methods?

Answer 14

@RepeatedTest

This annotation should replace @Test when used

Question 15

True or False

@WebMvcTest autoconfigures MockMvc

Answer 15

True

Question 16

When should you use @Mock or @MockBean?

Answer 16

@Mock should be used when no ApplicationContext is loaded. @MockBean should be used when an ApplicationContext is loaded

Question 17

The underlying component scan configuration of @SpringBootApplication defines exclude filters that are used to make sure slicing works as expected

Answer 17

True

Question 18

By default, @SpringBootTest will not call your main method, and instead the class itself is used directly to create the ApplicationContext

Answer 18

True

Question 19

Which Spring Boot starter is required to be on the classpath to test Spring MVC with WebTestClient?

Answer 19

Spring Boot Webflux

Question 20

What is the purpose of @ContextConfiguration?

Answer 20

To load and configure an ApplicationContext for tests

Question 21

What 2 annotations make up @SpringJunitConfig?

Answer 21

1. @ExtendWith(SpringExtension.class)
2. @ContextConfiguration