@DataJpaTest for repository testing in JUnit - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to annotate the test class for JPA repository testing.

JUnit

@[1]
public class UserRepositoryTest {
    // test methods
}

Drag options to blanks, or click blank then click option'

AWebMvcTest

BDataJpaTest

CSpringBootTest

DMockBean

Attempts:

3 left

💡 Hint

Common Mistakes

Using @SpringBootTest which loads the full context instead of a slice for JPA.

Using @WebMvcTest which is for controller layer testing.

The @DataJpaTest annotation is used to configure a test class for JPA repository testing with an embedded database.

2fill in blank

medium

Complete the code to inject the repository into the test class.

JUnit

@Autowired
private [1] userRepository;

Drag options to blanks, or click blank then click option'

AUserRepository

BEntityManager

CUserService

DUserController

Attempts:

3 left

💡 Hint

Common Mistakes

Injecting UserService or UserController instead of the repository.

Injecting EntityManager directly without repository.

The repository interface (UserRepository) is injected to test its methods.

3fill in blank

hard

Fix the error in the test method to save and verify a user entity.

JUnit

@Test
void testSaveUser() {
    User user = new User("john", "[e-mail]");
    userRepository.[1](user);
    assertThat(userRepository.findById(user.getId())).isPresent();
}

Drag options to blanks, or click blank then click option'

AsaveUser

Binsert

Csave

Dpersist

Attempts:

3 left

💡 Hint

Common Mistakes

Using saveUser which is not a JpaRepository method.

Using persist which is an EntityManager method, not repository.

The correct method to save an entity in JpaRepository is save().

4fill in blank

hard

Fill both blanks to write a test that finds a user by email.

JUnit

@Test
void testFindByEmail() {
    User user = new User("anna", "[e-mail]");
    userRepository.save(user);
    Optional<User> found = userRepository.[1]("[e-mail]");
    assertThat(found.[2]()).isTrue();
}

Drag options to blanks, or click blank then click option'

AfindByEmail

BisEmpty

CisPresent

DgetEmail

Attempts:

3 left

💡 Hint

Common Mistakes

Using isEmpty() which checks for absence, not presence.

Using getEmail() which is a getter, not an Optional method.

The repository method findByEmail returns an Optional; isPresent() checks if a value exists.

5fill in blank

hard

Fill all three blanks to write a test that deletes a user and verifies deletion.

JUnit

@Test
void testDeleteUser() {
    User user = new User("mike", "[e-mail]");
    userRepository.save(user);
    userRepository.[1](user);
    Optional<User> deleted = userRepository.[2](user.getId());
    assertThat(deleted.[3]()).isFalse();
}

Drag options to blanks, or click blank then click option'

Adelete

BfindById

CisPresent

Dremove

Attempts:

3 left

💡 Hint

Common Mistakes

Using remove() which is not a JpaRepository method.

Asserting isPresent() is true after deletion, which is incorrect.

Use delete() to remove the entity, findById() to check, and isPresent() to verify absence (assert false).