Spring DataJpa Test Tutorial : How to Test Database using Spring Boot @DataJPATest Annotation

#SPringDataJPATest #SpringBoot #UnitTesting #DataBase

► SUBSCRIBE & LIKE!!

► Important Information and code guide available bottom of the Description section

► Download the sample java microservice application :

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
► Here is our amazing playlist for Core Java, Spring MVC/Boot, Git and Microservice
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Watch my "Most Watched Videos"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Information
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@DataJpaTest is the annotation that Spring supports for a JPA test that focuses only on JPA components.

It will disable full auto-configuration and then, apply only enable configuration relevant to JPA tests. The list of the auto-configuration settings that are enabled can be found here.

By default, tests annotated with @DataJpaTest are transactional and roll back at the end of each test. If you don’t want it, you can disable transaction management for a test or for the whole class using @Transactional annotation:

@DataJpaTest
@Transactional(propagation = Propagation.NOT_SUPPORTED)
class YourNonTransactionalTests {

}
In-memory embedded database (like H2 database in this example) generally works well for tests, it is fast and does not require any installation. However, we can configure for a real database with @AutoConfigureTestDatabase annotation:

@DataJpaTest
@AutoConfigureTestDatabase(replace=Replace.NONE)
class YourRepositoryTests {

}

@DataJpaTest
class YourRepositoryTests {

}

TestEntityManager
The purpose of the EntityManager is to interact with the persistence context. Spring Data JPA abstractes you from the EntityManager through Repository interfaces. And TestEntityManager allows us to use EntityManager in tests.

We can inject a TestEntityManager bean in Data JPA tests. If you want to use TestEntityManager outside of @DataJpaTest instances, just add @AutoConfigureTestEntityManager annotation.

======================================
The job of @Controller is to create a Map of the model object and find a view but @RestController simply returns the object and object data is directly written into HTTP response as JSON or XML.
@Controller since Spring 2.5 Officially (3, 3.1) and @RestController Spring 4
@Controller is a common or generic annotation that is used to mark a class as Spring MVC Controller (web controller) while @RestController is a special controller used in RestFull Webservice API and the equivalent of
@RestController = @Controller + @ResponseBody
@Controller is a stereotype annotation or it’s specialization of @Component annotation, while @RestController is a specialization of @Controller annotation
@RestController and @Controller is that you don't need to use @ResponseBody on every handler method once you annotate the class with @RestController
Controller and @RestCotroller in Spring MVC is that once you mark a class @RestController then every method is written a domain object instead of a view.

Instagram: techtalk_debu

if you like my video, please subscribe to my channel and share the video

Thanks & Regards,
Debu Paul