CODEWITHSUNDEEP
javaunit-testing
NoSuchUserException
NoSuchUserException

Reputation: 149

JUnit using HyperSQL to test DAO classes

I did some research on how to test my DAO layer using HyperSQL and I found this question: https://softwareengineering.stackexchange.com/questions/219362/how-to-test-the-data-access-layer

How do I import DBConnection because I tried using hypersql jar and it did not work. In the question from the link I saw this db.url=jdbc:hsqldb:file:src/test/resources/testData;shutdown=true; but I do not know how to use it.

Upvotes: 1

Views: 1385

Answers (1)

AndyN
AndyN

Reputation: 2105

Using JDBC and Spring, in your application you'd be creating a DataSource object, and using that object to create a JdbcTemplate object, which is what you're using to run your JDBC queries. Similar to this example. So in order to use the HSql database, you'd need to change the values used to setup the DataSource bean but only for your unit tests.

Depending on how you're using Spring (annotations, xml config), there's a few ways of doing it. You'll need to create a new configuration bean, or configuration xml file, and then reference it in your unit tests.

For XML, copy over your spring context xml file, and change the DataSource values to something like:

<bean id="dataSource" 
  class="org.springframework.jdbc.datasource.DriverManagerDataSource">
  <property name="driverClassName" value="org.hsqldb.jdbcDriver"/>
  <property name="url" value="jdbc:hsqldb:file:src/test/resources/testData;shutdown=true;"/>
  <property name="username" value="SA"/>
  <property name="password" value=""/>

You'll then need to reference this new context config in your unit test. Something like:

@RunWith(SpringJUnit4ClassRunner.class)
// ApplicationContext will be loaded from "classpath:/test-config.xml"
@ContextConfiguration("/test-config.xml")
public class DAOTests {
    @Autowired
    private DatabaseDAO dao;
}

With annotations, you'll need to make a new configuration class (you should have one already, a class annotated with @Configuration) and return the appropriate DataSource. Something like this:

@Bean
public DataSource hsqlDataSource(){
    return DataSourceBuilder
        .create()
        .driverClassName("org.hsql.jdbcDriver")
        .url("jdbc:hsqldb:file:src/test/resources/testData;shutdown=true;")
        .username("SA")
        .password("");
        .build();
}

You can setup a profile for your configuration (using @Profile("test") annotation), and then specify which profile you want to use in your unit test (@ActiveProfiles("test")). More information here.

Alternatively, you could use the Spring EmbeddedDatabaseBuilder if you're just trying to do a simple DAO Test. There's a tutorial here. It sets you up with a HSql in memory database (as opposed to a file based one), which is very convenient for setting up / tearing down. Just add the bean to your configuration class, and your DAO should pick it up if Spring is injecting the DataSource for you. Example below taken from here

@Bean
public DataSource dataSource() {

    // no need shutdown, EmbeddedDatabaseFactoryBean will take care of this
    return new EmbeddedDatabaseBuilder()
        .setType(EmbeddedDatabaseType.HSQL)
        .addScript("db/setup_script.sql")
        .build();
}

There's a bit to Spring configuration management. I haven't covered it in much detail in this answer, but look up a few examples and it will start to make sense.

Upvotes: 1

Related Questions