How to have DBUnit @DatabaseSetup to happen before spring autowiring?

Question

Consider the typical DBUnit Spring Test (see https://github.com/springtestdbunit/spring-test-dbunit) :

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(locations = {
"classpath:/META-INF/spring/applicationContext-database.xml",
"classpath:spring-*.xml"
})
@TestExecutionListeners({ DependencyInjectionTestExecutionListener.class,
    DirtiesContextTestExecutionListener.class,
    TransactionalTestExecutionListener.class,
    DbUnitTestExecutionListener.class })
@DatabaseSetup("/dbunit/data.xml")
public class UnitTest {

    @Autowired
    private UnitUnderTest uut;

    @Test
    public void shouldInitDB() {
         ...
    }
}

What I have verified is that, and has expected, Autowiring will happen before DatabaseSetup. This must happen because DBUnit depends on the application context to provide the configured data source.

The problem is that the UnitUnderTest bean has a @PostConstruct where it loads some data from the DB but, since the Autowiring happens before the DBunit setup, the data will not be available at this stage.

Any ideas on how to solve this issue in a clean way?

It's really not a good solution but allowed me to move forward.Create a TestClass that inherits from the object to be autowired and expose a method for external initialization. Use in the @Before test. — Bruno Santos, Nov 09 '14 at 02:14
No solution so far. Not even a decent workaround. Will keep searching. — abdelrahman-sinno, Apr 01 '16 at 10:33

score 1 · Answer 1 · edited Jun 12 '17 at 12:15

You can you Spring's ResourceDatabasePopulator.

I think you can use something like this

@PostConstruct
public void myInMemryPopulator() {
final ResourceDatabasePopulator databasePopulator = new ResourceDatabasePopulator();

        try {

            Resource[] array = resourceResolver.getResources("classpath:/*.sql");       

            for (Resource resource : array) {

                databasePopulator.addScript(resource);
            }
            databasePopulator.populate(dataSource.getConnection());

        } catch (IOException | SQLException e) {
            LOGGER.error("Error in databasePopulator  {} ", e);
        }

    }

if still this not help. You can create Parent Test Case and add Static block in parent test case can call this method — Niraj Sonawane, Jun 12 '17 at 11:08

score 0 · Answer 2 · answered Nov 26 '13 at 10:07

0

You can have a setup method in your test class and call the post construct method manually. That will work.

answered Nov 26 '13 at 10:07

Eshan Sudharaka

607
2
9
16

I'm afraid that is a non-solution! In such case I would have to pass the responsibility of calling that method to some other bean. I don't think that there's the need to do that. I'm hopping that spring-test-dbunit will have a cleaner, less intrusive way of testing this kind of scenario, which I'm sure will not be that rare. – Bruno Santos Nov 27 '13 at 01:43
My postconstruct method tries to retrieve database object and it breaks while autowiring, so this solution won't help. – TheBakker Sep 04 '15 at 09:49

score 0 · Answer 3 · answered Mar 10 '22 at 21:15

0

Lazy initialization helped me, I added @Lazy over the @Component* and over the @Autowired in injection points

@Lazy
@Component
public class UnitUnderTestImpl {
...
}

@Lazy
@Autowired
private UnitUnderTest uut;

answered Mar 10 '22 at 21:15

tosha

1

How to have DBUnit @DatabaseSetup to happen before spring autowiring?

3 Answers3