Master Hibernate and JPA with Spring Boot in 100 Steps - FAQ 2 - When do We Need @Transactional in a Unit Test?

The video tutorial explains the importance of using transactions in unit tests, especially when making direct changes to the database. It highlights the role of the @Transactional annotation in ensuring that methods and their logic are executed within transaction boundaries. The tutorial also discusses how repository methods inherently handle transactions and the issues that arise when direct changes are made in unit tests without transactions. Finally, it provides guidance on using @Transactional to ensure that unit tests run within a transaction, maintaining data integrity.

Why is a transaction necessary when making changes to a database in unit tests?

• To ensure data consistency and integrity

• To reduce the amount of code needed

• To speed up the database operations

• To make the code more readable

What happens when a repository method is called from a unit test?

• The unit test must manually handle the transaction

• The repository method cannot be called from a unit test

• The transaction is ignored

• The transaction is automatically handled within the repository

What is the role of @Transactional in repository methods?

• It ensures that each method runs within a transaction

• It speeds up the execution of the method

• It makes the method more secure

• It allows the method to run without a database connection

What must be done when directly using the entity manager in a unit test?

• Add @Transactional to provide a transaction boundary

• Ensure the database is offline

• Use a different programming language

• Avoid using the entity manager altogether

What is the consequence of not using @Transactional when directly modifying the database in a unit test?

• The test will pass without any issues

• The database will automatically handle the transaction

• The changes may not be committed

• The test will run faster