Hi, I have been trying to use the utAssert.throws method within our test unit. I have followed the example in the documentation and have been unable to get it...
... Well, it won't work if it's a function, as the call gets executed as a piece of dynamic PL/SQL. It also looks like e_negative_value needs qualifying with...
Suppose I have a trigger named 'myTrigger'.
How does this play into the naming conventions?
Currently, I have my tests in a package called ut_myTrigger, but...
Chris, Not a bad fix, but it rather assumes the return type matches the global variable. What do you do when it doesn't? Declare more variables of given type?...
Padfield, James
jpadfiel@...
Jan 17, 2002 3:12 pm
59
While making utAssert.throws more sophistocated to either accept a return type as an argument would be great, I don't see it as a burden to add global...
I have found away to run unit tests in TOAD 7.2 from the toolbar or via a shortcut. To set this up: 1) Put the attached file somewhere like C:\utplsql 2) On...
Does utPLSQL analyze the code coverage ? Are there any freebies available for that ? It should mention how many lines of PL/SQL code is actualy tested by the...
... That is a wonderful idea, but it does not do so right now. How can we do this? Integrate with DBMS_PROFILER which DOES provide code coverage analysis. ... ...
... utplsql? Venky posted some code to do ref cursors : http://groups.yahoo.com/group/utPLSQL-Info/message/43 I haven't looked at it myself. He also has been...
Hello, I am relatively new to utplsql. I would like to be able to test my triggers. Does anyone have any suggestions as to how I could use utplsql for this? ...
Damon Torgerson
damon@...
Feb 6, 2002 4:36 pm
68
... You can only test procedures that are called from within your triggers, but there is currently no way to directly test a trigger within the test harness. I...
... Actually, while I don't have the code available -- I no longer work at the company -- I tested a series of triggers with the test harness. What I did was I...
Currently I am developing an application that can be used to managed non-fatal errors and data processing information. The app allows a user to define message...
For those of you using my script, or thinking about it, there is a minor change to the instructions. As pointed out to me by Jeff Smith at Quest, the script...
Sorry about this - another tweak to my script. It doesn't work properly
when the utplsql prefix contains '_' or '%', as it does by default. This
is because I...
I think this group will have to be renamed Chris'sToadScript-Info soon! I've made another minor change to the script, which can be downloaded from SourceForge....
I've used utPLSQL for a while - but I haven't yet bothered to figure this out. And, I'll admit, I haven't spent a huge amount of time in the documentation...
I have recently been reading Kent Beck's book "Extreme Programming Explained" on safari.oreilly.com, while trying out the free 30 day trial (I recommend taking...
Huzzah! - good points. I spend most of my time in Java and Junit and in practice don't have one TestCase per Class. I create testcases that make sense for...
... Actually, results are displayed with this query: SELECT * FROM utr_outcome WHERE run_id = l_id which means that there was no order enforced at all! That's...
... This is actually supported right now in utPLSQL. When I originally released the utility, you needed to make calls to utplsql.addtest to "register" the ...
Friends, As some of you may be aware, I have been working on utPLSQL, a unit testing framework for PL/SQL developers, for the last year or so. There are ...
The new version is available on SourceForge https://sourceforge.net/project/showfiles.php?group_id=6633 Have a look at the ChangeLog there, or the release...
I work for Oracle and we run all the Unit tests in the cron job. I was wondering if we can run the entire suite and get a HTML report out. ( with nice colors, ...
... Well, all results are actually stored in the utr_outcome table. I believe therefore that it would be rather straightforward for *someone* (ie, not me!) to...