Chat now with support
Chat with Support

Code Tester for Oracle 3.1 - Release Notes

Release Notes

Release Notes

Quest Code Tester for Oracle 3.1

Release Notes

6/19/2017

These release notes provide information about the Quest Code Tester for Oracle release.

About Code Tester 3.1

Code Tester for Oracle is a tool to help you test Oracle® code, written in the PL/SQL language. Code testing is generally acknowledged to be one of the biggest challenges and disappointments in the world of software.

We all know we should test our code. More than that, we all want to test our code, but there are many challenges to implementing a strong regression test of our code.

These challenges include having to write a large volume of test code, keeping that test code in synch with our application code as it changes, verifying the results of running our tests, and more.

Code Tester for Oracle tackles these challenges by making it easy to define your tests, generate your test code, and run the tests, all within an easy-to-use graphical interface.

The bottom line with Code Tester: you don't write test code. You describe your tests, and the tool then generates the test code (as a PL/SQL package) that implements your test definition.

Code Tester 3.1 is a minor release, with enhanced features and functionality.

New features

New features

A Team Coding feature was added to this release. Team Coding enables you to version your suites, test definitions, and test cases and store them in a version control system (VCS). To set up Team  Coding, follow these basic steps:

  1. Install a Team Coding repository: A Team Coding repository must be installed from Toad for Oracle on a local repository. Repositories on Toad Intelligence Central (TIC) are not supported.
  2. Configure Team Coding: A Toad for Oracle Team Coding Administrator must configure Code Tester Team Coding before users can work with it. To configure Team Coding, select Database | Team Coding | Configuration. The configuration involves:

    • Configure team settings: Select Team Settings from the navigation pane of the configuration window. Here, you select and configure the Version Control System (VCS) and set basic parameters for its use. These settings apply to all team members, regardless of their local settings (on the User Settings page).
    • Configure Team Projects: Select Team Projects from the navigation pane of the configuration window. At least one Team Project must exist for users to work with Team Coding. Name the project, select the version control system, and then select the test objects that you want to control in this team project.
    • Configure user settings: On the User Settings page, each user can set his or her own local settings if not set globally in the team settings.

The Team Coding implementation in Code Tester is similar to the one in Toad for Oracle, with the exception that Code Tester does not provide logging or compile options. For more information about using Team Coding, see the Toad for Oracle online help.

 

 

Enhancements

Enhancements

The following is a list of enhancements implemented in Code Tester 3.1.

Enhancement Issue ID

Expanded the capabilities of the Code Evolution module:

  • Code Tester tries whenever possible to keep values of inputs and outcomes when their data types are changed.
  • The Code Evolution module now can analyze not only the evolution of the data type itself but its dependencies too.
CTO-33, CTO-34
Added the ability to import Unit Tests from Quest SQL Developer. CTO-403
Added the SQL Developer import functionality into the command line application. CTO-426
Added LDAP support. CTO-401
Standard messages are now shown with a simple dialog rather than in the exception handler. CTO-282

Resolved Issues

Resolved Issues
Resolved issue Issue ID
Further improvements in Keep input and outcome values when Code Evolution modifies a test definition. CTO-217
Code Evolution with column type involved CTO-288
Test Builder should be able to be reconnected when Code Tester loses connection to Oracle. CTO-16
Unable to create test when the test program has a huge code CTO-440
Edit unit cases error after using Code Evolution CTO-242
Req_15: Increased Size Limit for VARCHAR2,NVARCHAR2, and RAW Data Types CTO-225
Further improvements in Keep input and outcome values when Code Evolution modifies a test definition. CTO-217
Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating