ansaurus

Question

Junit4 : expected=Exception not working with SPRING

Answer 1

+1 A:

Either you're running a unit test, in which case Spring TX shouldn't come in to play, or you're running some kind of integration test where you want to test what the save method does when your runtime exception is swallowed. I don't think anything is going wrong, you just need to make sure you understand what it is you are trying to test.

Paul McKenzie 2009-07-10 07:13:30

thank you Paul, if you look at the stack trace, I am running tests with SpringJUnit4ClassRunner, so Spring TX comes in play.It works with @NotTransactional annotation.

RN 2009-07-10 08:05:51

Well, exactly. Either run it with plain old junit and not with SpringJUnit4ClassRunner and test for runtime exception, or test for expected transactional behaviour.

Paul McKenzie 2009-07-10 08:22:08

Answer 2

+3 A:

Turned out that my first answer was wrong. Both @Test(expected=...) and @ExpectedException work, but there is some incompability between the Spring TestContext and Junit 4.5. Using Junit 4.4 solved the problem for me. Finally.

Bertolt 2009-09-11 13:57:54

Answer 3

A:

Here's a work-around I found to with Junit 4.5 - separate the @Transactional and @ExpectedException into nested functions. I guess the problem is something to do with the aop stuff spring puts around a @Transactional method.

@Test
@ExpectedException(org.springframework.dao.DataIntegrityViolationException.class)
public void Test10UniqueName()
{
    DoTest10UniqueName();
}

@Transactional
public void DoTest10UniqueName()
{
    final String NAME = "NAME";
    ProductCategoryDAO dao = DAOFactory.getProductCategoryDAO();
    ProductCategory test1 = new ProductCategory();
    test1.setName(NAME);
    ProductCategory test2 = new ProductCategory();
    test2.setName(NAME);
    dao.save(test1);
    dao.save(test2);
}

Brendan Richards 2009-11-30 11:30:16

ansaurus

tags:

views:

answers:

Junit4 : expected=Exception not working with SPRING

related questions