You can now download Code Tester 2.0. beta 2 from http://unittest.inside.quest.com/beta.jspa. We are making this beta available primarily to get your feedback on the overall direction of design and workflow. We look forward to that feedback, which you can post in the Beta discussion forum.

On 24 May 2010, I presented a one-hour webinar on some of the challenges we database programmers face setting up regression tests for programs that change database tables.

 

Here's the description:

"Most PL/SQL programs modify the contents of one or more tables. How can you verify that the modifications were correct? This is one of the biggest challenges facing PL/SQL developers. "Join Steven Feuerstein...

When it comes to making sure your program works as it should, there are two general categories of test cases:

Tests of requirements: every requirement needs to have at least one test case devoted exclusively to verifying that the requirement has been met: the code performs as required. If you don't test for a requirement, then you do not know if it works. It is, ahem, theoretically correct. In other words, it is very likely buggy....

Having just released version 1.9.1 of Quest Code Tester, our development team is now hard at work on Code Tester 2.0 (tentatively scheduled for release in late Q3 2010).

We are still in the very early stages of our work, but I thought it would be helpful to share some of our concepts and general direction with you - and to ask for your feedback.



I will post this document in the Code Tester forum under...

by Steven Feuerstein

An object type is Oracle's version of an object-oriented class. It shares some of the features of a class, but falls a bit short. In Code Tester 1.9 and higher you can define and run tests for methods of an object type. You can also directly test the contents of an instance of an object type.



Click here...

Getting a happy green face after running your tests is, of course, very important. It is also important, however, to understand how much of the code in your program is being exercised by your tests. If, for example, you discovered that all your tests are successful, but only 10% of the lines of code in your program are actually run, you would have to conclude that either your tests are inadequate or you wrote a lot of code...

Written by Finn Ellebaek Nielsen. A short introduction to Continuous Integration (CI) and a description of how to integrate testing Oracle code with QCTO in a CI environment.

Sometimes you need to reference the value of an IN argument (an input, in Code Tester terminology) in your outcome. For example, under certain circumstances, the string returned by your function should be the same as the input value. Or perhaps the out value should be some part of the input value.

You could hard-code the same value you supplied in the Input Grid, but then if you change the input value, you have to...

Did you know that in Code Tester 1.8.5 you can now perform in-line validation of your customization code? For more complex tests, this will save you lots of time and make it easier to build your regression tests.

 

The ultimate objective of Code Tester is easy to state: allow developers to test arbitrarily complex PL/SQL programs without writing any test code....

In case you missed my announcement on the Code Tester community forum, we have now posted a beta version of 1.9.

 

The major focus for 1.9 to date has been to add support for automated testing of object type methods. This beta release offers the first glimpse of this functionality; you should now be able to define tests for constructors, static methods, and member procedures and functions.

...

Written by Steven Feuerstein   Code Tester is a relatively young tool (first released for production use in February 2007), but it has matured quickly (hey, at least I think so!) and is packed full of handy features.

 

As with all other tools, however, it can sometimes be hard to find the "jewels," so I thought I would highlight a couple.

 

1. Dynamically generated test cases

 

Rather...

Written by Finn Ellebaek Nielsen. Learn about automated testing and much more at the OPP2009 conference November 10-11 in Atlanta, Georgia, USA.

Written by Finn Ellebaek Nielsen. Best practices for determining test amount required through analysis of product risk.

Written by Finn Ellebaek Nielsen. Best practices for a test approach that implements the strategy and test policies for Oracle code laid out in a previous blog post.

Written by Finn Ellebaek Nielsen. Best practices for establishing a test strategy, as well as test policies for Oracle code.

Written by Steven Feuerstein. Version 1.8.3 of Quest Code Tester is now available.

Written by Finn Ellebaek Nielsen. Reasons for testing Oracle code in the database.

Written by Steven Feuerstein. Introduction to the "Real Automated Code Testing for Oracle" blog.