Question

I am in reference to Spring Roo In Action (book from Manning). Somewhere in the book it says “Roo marks the test class as @Transactional so that the unit tests automatically roll back any change.

Here is the illustrating method:

@Test
@Transactional
  public void addAndFetchCourseViaRepo() {
    Course c = new Course();
    c.setCourseType(CourseTypeEnum.CONTINUING_EDUCATION);
    c.setName("Stand-up Comedy");
    c.setDescription(
      "You'll laugh, you'll cry, it will become a part of you.");
    c.setMaxiumumCapacity(10);

    c.persist();
    c.flush();
    c.clear();  
    Assert.assertNotNull(c.getId());

    Course c2 = Course.findCourse(c.getId());
    Assert.assertNotNull(c2);
    Assert.assertEquals(c.getName(), c2.getName());
    Assert.assertEquals(c2.getDescription(), c.getDescription());
    Assert.assertEquals(
      c.getMaxiumumCapacity(), c2.getMaxiumumCapacity());
    Assert.assertEquals(c.getCourseType(), c2.getCourseType());
  }

However, I don’t understand why changes in this method would be automatically rolled back if no RuntimeException occurs…

Answer 1

Quote from documentation:

By default, the framework will create and roll back a transaction for each test. You simply write code that can assume the existence of a transaction. […] In addition, if test methods delete the contents of selected tables while running within a transaction, the transaction will roll back by default, and the database will return to its state prior to execution of the test. Transactional support is provided to your test class via a PlatformTransactionManager bean defined in the test’s application context.

So, in other words, SpringJUnit4ClassRunner who runs your tests always do transaction rollback after test execution.