DATAJDBC-346: Fixed test failures when using MSSQL database

[sachouche]

Analysis -

• Test failure have been observed with tests that were aimed to be only executed with the HSQL database
• There were two reasons for such failures
• a) The current infrastructure will need to instantiate a data-source for each executed test; this means that HSQL database based tests still require valid MSSQL scripts to be available (valid and not-empty)
• b) We need skip logic for HSQL based tests called with different environments

FIX

• a) Added database scripts to avoid data source initialization failures
• b) Added skip logic by following the same pattern that have been utilized on other tests

[pivotal-issuemaster]

@sachouche Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

[pivotal-issuemaster]

@sachouche Thank you for signing the Contributor License Agreement!

[schauder]

Thanks for looking into this.

There is an easier way to disable HsqlIntegrationTests for all databases except HSQLDB:
Just add @ActiveProfiles("hsql") to the test as done in MyBatisHsqlIntegrationTests.

This should also negate the need for other database setup scripts

[sachouche]

@schauder, thank you for the feedback! your suggested fix is definitely more elegant and easier to maintain. The only test where I had to add more logic is the "EnableJdbcAuditingHsqlIntegrationTests.java" test since the logic programmatically creates new contexts..

[sachouche]

@schauder, I have implemented your requested changes; can you please review them?

Thanks!

[schauder]

That's merged.

Thanks.