Menu
▾
▴
#3 Help with reporting output
I'm new to using utPLSQL and am trying to figure out the best way to report testing results. I've already created and run a couple of test packages, and that looks fine. However, the packages I'm testing already contain lots of dbms_output statements for debugging purposes, so the result is a lot of output in addition to what is generated through the utPLSQL framework. My question is, what are some suggested methods for reporting this? If I'm just running the tests manually on my own, display output is fine. But what if I want something more simple that just shows me only what is reported by utPLSQL? I've read through the documentation on the utResult package but it's not clear to me how to use this, or if it's primarily for use with some sort of reporting interface.
Also, the goal is to eventually make this part of a build process. What would happen is that as soon as we upload a new version of a package to the test server, the unit testing process would kick off. Or this could be done manually. From what I've read it looks like output can be generated to an Oracle directory, and at that point maybe read or emailed by some other process? Just looking for recommended or best practices. Thanks.
Have a look at the Custom Reporter Packages page. Basically, your options are the default DBMS_OUTPUT or writing a file - either plain text or HTML. Or you can always write your own custom reporter if you find something else works better for you (in which case, please feel free to contribute it back to the project so others can benefit :) )
No recent contact, closing ticket. Please raise a new ticket if you would like any further help.