utPLSQL logo

[ Home | Getting Started | Build Test Packages | Examples | User Guide | Release Notes | Document Map ]

< Previous Section: utRecEq Package | Next Section: Custom Reporter Packages >

Defining Test Suites

If you define test suites and register packages within those suites, then utPLSQL will run an unlimited number of tests with a single command.

Note

utSuite - Define Test Suites

To create and remove test suites, call these programs:

PROCEDURE utSuite.add (
   name_in          IN VARCHAR2,
   desc_in          IN VARCHAR2 := NULL,
   rem_if_exists_in IN BOOLEAN  := TRUE
);

PROCEDURE utSuite.rem (name_in IN VARCHAR2);

These programs manipulate the contents of the ut_suite table. See the tables.sql file for the DDL creating this table.

utPackage - Define Test Packages for a Suite

To register a package in a suite, call the following:

PROCEDURE utPackage.add (
   suite_in          IN VARCHAR2,
   package_in        IN VARCHAR2,
   samepackage_in    IN BOOLEAN := FALSE,
   prefix_in         IN VARCHAR2 := NULL,
   dir_in            IN VARCHAR2 := NULL,
   seq_in            IN PLS_INTEGER := NULL,
   owner_in          IN VARCHAR2 := NULL,
   add_tests_in      IN BOOLEAN := FALSE,
   test_overloads_in IN BOOLEAN := FALSE
);

This manipulates the contents of the ut_package table. See the tables.sql file for the DDL creating this table.

Here is a sample script that defines a very small portion of the PL/Vision test suite:

BEGIN
   utSuite.add ('PLVision');

   utPackage.add('PLVision', 'PLVstr', dir_in => 'e:\utplsql\test');

   utPackage.add ('PLVision', 'PLVdate', dir_in => 'e:\utplsql\test'');

   utPLSQL.testsuite ('PLVision', recompile_in => TRUE);

END;
/

< Previous Section: utRecEq Package | Next Section: Custom Reporter Packages >

utPLSQL logo

Valid XHTML 1.0 Strict