1

I am currently working on a project where we need to test the database packages and functions. We need to provide the input parameters to the database package and test the packages returns the expected value, also we want to test the response time of the request.

Please advice, if there is any tool available to perform this or we can write our test cases in Junit or some other framework. Which one will be best approach?

Nikunj Aggarwal
  • 754
  • 2
  • 12
  • 32

2 Answers2

0

I've used a more native approach when I had to do DWH testing. I've arranged the Test framework around the Dev data integration framework that was already in place. So i had a lot of reusable jobs, configurations and code. But using OOP like you suggest

write our test cases in Junit

is a way to go too. But keep in mind that very often the DWH design is very complex (with a lot of aspects to consider) and interacting with the Persistence layer is not always the best candidate for testing strategy. A more DB oriented solution (like tSQLt) offers a significant performance.

enter image description here

Those resources helped me a lot:

ekostadinov
  • 6,880
  • 3
  • 29
  • 47
0

My framework Acolyte provides a JDBC driver & tools, designed for such purposes (mock up, testing, ...): http://tour.acolyte.eu.org

It's used already in some open source projects (Anorm, Youtube Vitess, ...), either in vanilla Java, or using its Scala DSL.

handler = handleStatement.withQueryDetection(...).
  withQueryHandler(/* which result for which query */).
  withUpdateHandler(/* which result for which update */).

// Register prepared handler with expected ID 'my-unique-id'
acolyte.Driver.register("my-unique-id", handler);
// then ...
Connection con = DriverManager.getConnection(jdbcUrl);
// ... Connection |con| is managed through |handler|
cchantep
  • 9,118
  • 3
  • 30
  • 41