A developer recently contacted me with these questions:
I’ve been asked to find out/evaluate about PLSQL Testing frameworks for the project I currently work on for the last few days for Monday morning, with a view to possibly using an automated tool.
I’m looking to find the best way to automate testing of PL/SQL code. The technical aspects of an approach, associated costs involved, etc.
The tools I’m aware of are utPLSQL and Ounit, QUTE, Quest Code Tester for Oracle, PLUTO and DBUnit. I have been googling, not much good info on PLUTO and we have used DBUnit, but it requires alot of script writing.
Information I’m looking for each one:
- Alliance with xUNIT, anything that may be interesting as a selection criteria.
- Whether they are based on utPLSQL, or what approach they use if this is useful
- How they might integrate with Junit, as a calling framework.
- Support they provide within tests eg: exception comparisons, resultset comparison, data comparisons, ref cursor support and comparison, dynamic SQL support.
- anecdotal support for usability ie: usage and whether they are problematic
- If open source is there a large community associated, forums etc…
I’ve come across alot of info on utPLSQL and Quest Code, but’s it’s important that an automated solution can integrated into Junit as a calling framework (My Technical manager’s words).
We are also using CI Cruise Control to run our Java tests to produce build test reports.
We currently have crudely integrated our PLSQL tests into Junit by simply calling the procedures and then compare current .out files with a previous .out.good file and if they match then tests have passed, but this assumes one as validated the previous good file.