Support for Oracle 11g

You can now use Code Tester with Oracle 11g, with the following restriction: the RESULT CACHE clause will have to be commented out of your program headers for the initial creation of your test definition.

46148

Code Tester now asks the user to confirm that they wish to delete the current test definition when they request creation of a new test definition for a program that already has a test definition.

46152

Specification of random values for dates on the same day now works properly.

46173

If a test case has a conditional execution clause that returns FALSE, generate outcomes does not show any outcomes because it stops execution.

46234

Save as Quick Build is NOT saving/transferring test case customization logic.

46690

Errors importing multiple files when full path does not have spaces.

46772

Regenerating test code with dynamic Test Cases fails with compile errors.

46900

Pre-execution customization code was not properly written to the export file, resulting in possible loss of customization code.

47137

Incorrect line breaks in generated code was causing compile failures.

47159

Make visible the name of the input argument variable on the Test Editor properties window for ALL TYPES.

47288

Invalid test code was generated when the first column of a table being tested was not comparable (CLOB, LONG, type, etc.).

47400/

47227/

47778

You can now use the decimal separator character native to your dataset. Previously, Code Tester required the use of the "." as the decimal separator.

47465

"Dataset contains no rows?" shows wrong message when the test is successful.

47472

Error when a test definition has a custom Test Data Group query on the outcome side of an IN OUT argument.

47513

Empty values for min and max precision for random numbers causes an exception.

47527

If I have multiple values for the outcome of an IN OUT argument, then the input value for the argument is changed to the valued RETURNED by the program, for the next call to the program.

47530

Mutating trigger error when changing a random Test Data Group.

47617

Export of attribute rows does not include the valueN_is_expr values.

47598 

Customization code that contains a line with just one single quote is incorrectly displayed.

47779

You can no longer run a unit test or test case from the Test Editor browser if it has been marked inactive.

47780

Running a test from a script caused a "Run universal ID cannot be NULL" error.

48050

When copying a test case, some data was not copied properly, including customization code and conditional execution logic.

48361

Variables bvased on arguments of NATURALN or POSTITIVEN type now are assigned a default value.

48400

COUNT = tests for a query that contains a local variable reference now work properly.

48650

Single Value Query tests for queries with references to PL/SQL variables cannot generate code, due to validation warnings.

48751

Leading blanks are being trimmed from the user's input. They are now retained.

48815

Export of test definitions fail with VALUE_EROR exception due to a large number of "/" characters in custom code.

48860

Very large export files due to inclusion of the snapshot of source code.

48945

Even when a test definition is marked as Stable, Code Tester is regenerating the test code.

48946 

Test Editor copy of test case leaves off datatype resulting in invalid test code.

Display of test definitions inside suites

The schema drop-down determines which programs and suites you can see in the lists (only those created in that schema). This means that if your suite contains programs owned by more than one schema, you will not be able to see/run all those programs in the suite. For now, you should create a separate suite for each set of programs defined in a given schema.

Unicode Support

Code Tester should work correctly when the database server character set is defined as multi-byte, the client is defined as single-byte, and all characters used to name database objects use a subset of the single byte character set in use on the client. Extensive testing has not been performed on this configuration.

Entering SELECT Statements

When you enter a SELECT statement for a query, that query must not have any leading comments. Nor can it have a terminating semi-colon. These will cause compile errors in the resulting test code.

Support for CLOBs

Unsupported Datatypes

Quest Code Tester will not be able to build tests for arguments of the following types:

• Object type methods

• BLOB, LONG and LONG RAW

You will need to write your customized tests against these elements, by either defining an expression or Boolean outcome and then building all the necessary code to define the test.

When testing the contents of tables, views and queries, Code Tester can only analyze the contents of columns that can be referenced in UNION and MINUS operations. So, for example, a table with a CLOB column cannot be directly analyzed for equality with another dataset.

Code Tester will automatically ignore any columns that cannot be used in the comparisons.

Testing contents of tables with non-scalar columns

Quest Code Tester does not perform dataset comparison checks for tables with CLOB columns and other complex datatypes. Instead, Code Tester will automatically ignore any columns of these types that cannot be used in the comparisons.

Test data values consisting of very large strings

When you are comparing record contents to a query, the column names in the query must match those of the record field names. Then the automatically generated records-equal function will compile and work properly.

Quest Code Tester performs some basic analysis to determine if you have sufficient tablespace available to install the product. This calculation is not always accurate, however, you may run out of space. The installer will notify you that the installation fails, but it will not report specifically on this error. If you have an install error, please check the qu_install.log file for tablespace errors. If present, you will need to install into a different tablespace or ask your DBA for more space.

Creating test definition by two different users

You can encounter a blocked Quest Code Tester session by doing the following: user A starts up Test Builder for program XYZ, to create a new test definition for this program. User B then tries to open Test Builder for the same program. User B will be blocked until user A completes their work. Then user B will receive an error, because the test definition already exists (by this time).

If your IN argument is an object type, you cannot specify an input value directly. Instead you must write the assignment to set up that input value via initialization code (at the input or test case levels).

The schema in which you install Quest Code Tester must have these privileges:

CREATE PROCEDURE

CREATE SEQUENCE

CREATE SESSION

CREATE SYNONYM

CREATE TABLE

CREATE TRIGGER

CREATE VIEW

CREATE TYPE

Note 1: Quest Code Tester will create a schema with the necessary privileges as part of the installation process, when the create new user and install into new user schema option is selected on Step 2 of the Repository Wizard.

Note 2: We recommend that you install Quest Code Tester into its own schema, and create public synonyms so that all developers will be able to use Quest Code Tester and share their test definitions. This will also help you keep application code distinct from the Quest Code Tester code base. To do this, your schema must also have CREATE and DROP PUBLIC SYNONYM privileges.