To install/upgrade, download the latest Release
Also see the compatibility page in the wtPLSQL repository wiki.
Use GitHub "issues" for support. A (free) GitHub account will be required to create a new issue. Issues can be searched without an account.
This is the summary from the WT_ASSERT package self-test. This is the default DBMS_OUTPUT format.
wtPLSQL 1.1.0 - Run ID 422: 20-May-2018 03:39:54 PM
Test Results for WTP.WT_ASSERT
Total Testcases: 150 Total Assertions: 404
Minimum Elapsed msec: 0 Failed Assertions: 0
Average Elapsed msec: 7 Error Assertions: 0
Maximum Elapsed msec: 1134 Test Yield: 100.00%
Total Run Time (sec): 2.9
Code Coverage for PACKAGE BODY WTP.WT_ASSERT
Ignored Lines: 1103 Total Profiled Lines: 1464
Excluded Lines: 6 Total Executed Lines: 309
Minimum Elapsed usec: 0 Not Executed Lines: 0
Average Elapsed usec: 3054 Unknown Lines: 46
Maximum Elapsed usec: 332876 Code Coverage: 100.00%
Trigger Source Offset: 0
To view the complete test results from the wtPLSQL self-test, go to the test_allO.LST file in GitHub.
wtPLSQL helps with white-box testing of Oracle database objects. It is particularly well suited for unit testing and simple integration testing. It is written in PL/SQL. It contains a self-test which makes it easier to support and customize.
Like utPLSQL, wtPLSQL provides a set of assertion tests that can be used to determine how well an Oracle database object is performing. These assertions record the outcome (success or failure) of each test. These assertions also record the time between calls. A test runner (PL/SQL package) must be created with these assertion tests included. When the test runner is executed, the outcome and timing of the assertion tests are recorded. The Core Features page introduces the main functionality of wtPLSQL.
A simple text based reporting package called "WT_TEXT_REPORT" is included with the core installation. Custom reports are easy to create because the outcome and timing data is stored in the Oracle database. A set of DBDocs and E-R diagrams are provided to assist with any reporting customization.
Because wtPLSQL is for PL/SQL developers, a Best Practices page has some guidance for creating Test Runner packages in PL/SQL.
The About page has more information about the history and testing methodology of wtPLSQL.
The Definitions page includes definitions from many sources to help define the terms used in various software testing methodologies.
utPLSQL V3 is an excellent choice for unit testing. It is well supported and includes extensive functionality.
wtPLSQL has a different focus than utPLSQL V3. More information is available in this link.
Help us improve by joining us at the wtPLSQL repository.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.