Welcome to Quest Code Tester for Oracle

Quest 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.

Quest 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 Quest 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.

New for Release 1.8.4

In-place validation of custom code	Code Tester now allows you to perform in-place validation of customization code. You no longer have to generate the test code in order to see compilation errors in your custom code.
Support Bundle contains additional information	The Support Bundle trace file now includes the contents of the Code Tester error tables (qu_err_instance and qu_err_context), as well any compilation errors in my_codetester and repository packages.
Additional validations in Test Builder	1. The variables names for the "from program" and "expected result" data in an outcome cannot be the same. 2. All inputs in a test case must have unique variable names. 3. A query cannot contain a CURSOR expression.
Override the datatypes or columns in a query	Users can override the datatypes for columns in a query to ensure that the correct types are used. This is critical when you are selecting columns of NVARCHAR2 type, due to a bug in Oracle's DBMS_SQL.DESCRIBE_COLUMNS procedure. See the FAQ for instructions on how to do this overriding.
Viewing suites test definitions	You can now see and run suites as long as that suite contains at least one test definition that you have the authority to execute. You will not be able to execute test definitions in the suite that you do not have authority to execute.
Warning for CREATE TYPE privileges	The user is now warned inside Test Builder if she lacks the CREATE TYPE privilege needed to do the requested dataset comparison.
Referencing PL/SQL variables within queries in outcomes	You can now reference PL/SQL variables within queries in outcomes, and you do not have to request "Ignore warnings" or mark the query as an expression.
Silent Installation	You can now use the command line for silent installation.

New for Release 1.8.3

New Export/Import Architecture	Code Tester now writes export files as an XML document. It will import both the legacy ".QUT" export files as well as the new .XML formatted files. Merging is only support for XML exports.
Expanded Set of "Hooks"	Code Tester now offers a greatly expanded set of hooks via the my_codetester package to customize the behavior of Code Tester at key points like before and after import, before and after running a test, etc.
Reports for Suites	All reports defined for individual test definitions are now available for suites as well.
View All Test Definitions in Test Dashboard	You can now change the schema selector to "All Schemas" so that you can see the list of all test definitions to which you have access (run and/or edit) at once, without changing the selected schema.
Use Windows Name to Track Changes to Test Definition	You can use the my_codetester package to specify to Code Tester that the "created by" and "changed by" audit columns on test definition tables be populated with the name of the Windows user, rather than the Oracle schema name returned by the USER function.
Test Package Formatting on Demand	Code Tester will no longer automatically format the generated test code (this will improve overall performance of generation). You will now need to explicit request a format and recompile in the Test Code tab of Test Editor.
Improved Support for Wider Set of Datatypes	Code Tester will now allow you to create test definitions properly for all kinds of timestamps and intervals. You can also create a test definition for an object type, though you will still need to write the actual test logic yourself.

New for Release 1.8.2

Greatly Expanded Set of Built-in Reports	This release of Code Tester offers a wealth of new reports and fixes some bugs and improves content in existing reports. New reports include: code coverage analysis that rolls up to a subprogram and the entire package; test coverage reports that show how many of your programs has tests defined on them; code not executed (inverse of code coverage); incomplete test definitions; out of date test definitions.
Specify the Authid setting for the test package	You can compile a PL/SQL package with AUTHID DEFINER (the package executes with the privileges of the definer or owner of the package) or AUTHID CURRENT_USER (the package executes with the privileges of the invoker or caller of the package). Prior to 1.8.2, Code Tester always created the test package with the same AUTHID setting as the program being tested. Now, you can specify a particular AUTHID setting for an individual test definition or as a Quest Code Tester-wide preference. This is useful when you have set up a separate schema to own all test code, which will be called from the application code schema.
Change Schema and Program Names in Test Editor	Prior to Oracle 1.8.2, you were not allowed to change the names of the schemas and programs being tested or of the test package generated. You had to change these values by editing the underlying table directly. Now, you can make the changes directly in the Test Editor.
Specify Override Schema Name for Test Package	By default, your test package will be compiled into the schema specified by the test definition properties (which you can change in Test Editor). If you want that test package to be compiled into a different schema, such as a centralized schema for all test code, you can provide an override schema name that will be applied to all schemas.
View Source Code in Test Builder	You can now view the source code you are defining tests in the Test Builder.
Use Positional Notation to Call Tested Program	By default, Code Tester uses named notation (formal => actual) to call your program from within the test package. For some package overloading, named notation actually results in ambiguity. If this occurs with your package, you can specify that you do not want named notation and instead positional notation will be used.
Expanded Options for Export and Import	Both the export and import windows now offer additional flexibility, including: enable/disable exporting of results and source code; specification of the schema name for both the tested program and the generated test package; importing of multiple test definitions.
Specify Code Coverage Data Gathering in Test Editor	Prior to Quest Code Tester 1.8.2, you had to include code in a customization section to enable the gathering of PL/SQL profiler data (used to generate code coverage reports). Now, you can specify this data gathering from within Test Editor at any one of three levels: test definition as a whole (all unit tests), a specific unit test (all test cases within that unit) and a specific test case.
Specify Commit and Rollback Activity	Prior to Quest Code Tester 1.8.2, you could modify the default transaction activity (a rollback before each test case) only by adding code to a customization section. Now you can specify both rollback and commit activity, before and/or after test case.
Check for Equality/inequality of Booleans	You can perform a direct check between two Booleans for equality and inequality. Previously, you could only specify that a Boolean changed by the program was TRUE, FALSE or NULL.

Resolved Issues

The following provides a list of issues fixed.

Bug	Description
47,138	Function added to qu_helper_file to return number of lines in file, along with other useful file-related utilities.
48,598	When the Changed By Program datatype is the Test Builder Outcome Grid is changed, the test type field is not updated.
51,936	Provide a mycodetester function to allow bypassing of test definition validation. That way, if there is a bug, Code Tester can save changes and allow the user to continue.
52,692	Large integer values are being forced to display in scientific notation. Instead, the value should remain in the form entered by the user.
54,907	The outcome automatically created for an OUT argument of type object type results in a list index out of bounds error when I try to set the test type.
55,961	Fix many UI "glitches," in which portions of labels or fields are truncated.
55,962	Automatically remove trailing ";" from queries so that the resulting generated test package compiles properly.
56,129	Code Tester does not reinstall synonyms after upgrade.
56,766	Export suite with set the owners to "same as current owner" and the resulting export file is not valid.
56,769	Unique index violations errors on suite import caused failures in the import process. Errors raised for the UN_QU_SUHA_GUIDS index.
57,108	Numbers with large numbers of digits are rounded up to the nearest 10000. The values provided by the user should not be changed.
57,185	Blank lines are being added to formatted initialization and cleanup code in Outcomes.
57,240	Very slow performance when pressing on name of unit test in Test Editor.
57,249	The message for row count comparison for a "Table is unchanged" test is wrong.
57,250	Changes made to table by tested program are being committed even though there is no commit in the program itself.
57,457	The installer will no longer force the customer to Remove through the Microsoft MSI interface if Code Tester is already installed and is being upgraded.
57,532	If user has a licensed version of Code Tester and then tries to upgrade with a trial version, the licensed key is gone and replaced by the trial key.
57,863	User cannot open test Builder for a packaged program that relies on a subtype that is based directly or indirectly on a subtype of integer (binary_integer, pls_integer, etc.).
57,974	Trap and support testing of errors that are raised by invalid argument values, rather than reporting the test as a Runtime Failure.
58,286	"List index out of bounds" error is raised when attempting to work with an object type.
58,359	The MINUS UNION logic to compare datasets does not correctly identify differences when tables have certain combinations of duplicate rows.
58,394	The schema names for test definitions in suites are set properly on import, with the result being that you cannot see the test definitions in the suite.
58,415	The owner for the test package is begin set incorrectly to the schema that owns the Code Tester repository.
58,490	Enter a value of 1 for the error code in an exception outcome and Code Tester raises an exception.
58,515	The "does not contain" test for strings is not working properly. I ask if "aa" does not contain "aa" and it says YES.
58,591	Packages with procedures whose names are 29 or 30 chars in length cause a VALUE_ERROR exception.
58,620	Infinite loop when running Code Tester from a command line and the Code Tester repository is not found.
58,812	Command line option /T=<param> works improperly. Instead of searching test definition defined by <param> it looks for tested program and treats the <param> as its name.
58,909	If I activate a test case in test builder or test editor, but the unit test is also set to inactive (all test cases previously were inactive), then the UT is NOT set to active, which it should be.
58,920	Access violation occurs when you open Test Editor for an existing test definition, delete all unit tests and then press Ctl-B to open Test Builder.
58,921	Single line comment at end of query with count = 0 test caused compilation error.
58,935	Support bundle wizard closes before support bundle is created and sent or saved.
59,025	Description of result for timestamp comparison shows wrong information.
59,076	Toolbar changes are not saved when Code Tester is closed. We should preserve user preferences in all windows.
59,086	Distinguish more clearly in results between true NULL and strings that are "NULL" or "null" etc. Users can now specify the string that they want used to display a NULL value.
59,152	CLOB comparisons when differences are > 32K are not detected (different clobs are found to be equal).
59,230	Do not always display generate option window when user explicitly requests generation. Users can now check a box to avoid seeing this window. This setting is reset each time to restart Code Tester.
59,315	Programs with ANYDATASET or ANYTYPE argument causes error when starting Test Builder.
59,336	The Raises Any outcome incorrectly shows failure when an exception was raised.
59,345	Fix validation so that a user cannot create more than one exception outcome for a test case.
59,347	Custom exception code that does not start with EXCEPTION causes compile error.
59,380	Nested tables must be initialized when they are declared locally inside the test code. That way, in the init section, you just extend and assign values.
59,390	Merge of test definitions when programs are owned by different schemas causing problems.
59,420	Do not create default/initial outcomes for any OUT or IN OUT (or RETURN) argument whose datatype is unsupported (object type, any data, etc.).
59,450	Do not try to grant privileges on packages like qu_utplsql_api and xml packages, when they might not exist.
59,465	Two definitions for the "same" program (same name) owned by different schemas, with same test definition owner: one runs, the other does not.
59,493	Create a test definition for a program that already has a test definition owned by another, and when I ask to run, it tries to generate/run the other test definition (for which I don't have privileges to generate).
59,587	If test editor is open for program A, and then I import a suite that includes A, Code Tester deadlocks.
59,593	Import error occurs if I try to import for an existing test definition, but the test definition package name is different.
59,631	A cursor variable test (= table or = query) which returns non-comparable column values like CLOBs has runtime errors.
59,633	A query control (expected result) that has a new line character directly after SELECT causes invalid code generation.
59,645	After an upgrade, private grants were no longer in place.
59,949	Report "Test Coverage for All Code in Selected Schema" does return result
60,053	Customer running Vista is unable to write to the INI file. Seems to be in the wrong location; make sure that Code Tester correctly uses the roaming profile.
60,127	"File is unchanged" test is failing because (a) the template was bad and (b) file that was copied (temporary) is still locked/open.
60,247	The results report does not show any outcome information - AT ALL.
60,589	Unable to build a test for UTL_FILE.FOPEN.
60,838	If user chooses to recompile test code, then if it is out of date, do a silent generation first.
61,137	Show better error message when export is too big, causing a memory error.
61,310	Generated dynamic test case that checks "count after > count before by 1" does not correctly calculate the count before each generated TC. Instead it is done just once, leading to incorrect results.
61,427	Do not regenerate and recompile when running a test if the test definition is stable.
61,533	IN parameters do not always appear in the correct order.
61,901	Parameters of type RAW are not properly recognized when they are defined through a subtype or %type.
61,903	Datatypes with more than one word (INTERVAL, TIMESTAMP WITH...) are not parsed properly. Only the first word (at best) is saved. For INTERVAL, the type is not extracted at all.
62,067	Date entered by user is not saved properly in input or outcome grid, due to non-default regional settings.
62,232	Previously documented transaction mgt behavior (rollback before TC and after) is changed in 1.8.2 to only rollback before. This causes existing tests to fail. Change default to rollback before and after.
62,250	Code Tester raises an access violation error when attempting to drag and drop test definition to suite folder.
62,306	User is unable to generate a test package that has no prefix (the default is Q##).
62,314	Try to run a suite that has at least one test definition for which the program is not defined (and therefore invisible in the dashboard), you get an access violation when you try to run the suite.
62,317	Create outcome for table with RAW column and Test Builder tells us that the list of columns are incompatible.
62668	The wrong parameters are displayed in the input grid of Test Builder for packages with many subprograms that contains the same initial letters.
62573	Object type creation fails dataset comparisons of tables with large numbers of columns.
62398	Reports run at the unit test and test case levels raised errors.
62397	Test code compilation errors occurred for program units with non-standard Oracle identifier names (contained with double quotes).
62326	Access violation is raised when using command line execution and these three commands in sequence: /Delete /Import /Run
63491	Parameters with types defined by %ROWTYPE, %TYPE or subtypes in another schema are now correctly defined within Code Tester. That is, the schema name is added as a prefix to the type.
63384	Multiple outcomes or inputs that have the same variable name will no longer result in invalid test code. Each variable is now declared in its own scope.
63155	Generate Outcomes now correctly displays and saves as an outcome a NULL value instead of the null indicator string, whose default value is currently "{null}".
59261	Expressions based on cursor variable types no longer raise a validation error, unable to find the template for the outcome.
59678	Pressing a key in the list of package subprograms at the top of Test Builder no longer raises a "List index out of bounds" error.
63280	Errors raised when running the Generate Outcomes code are now displayed, so the user can see possible syntax errors in any custom code they provided.
63828	Inconsistent format masks for timestamps with and without timezones. They are now consistent across reports and Results Viewer display.
63727	A multiline comment (/* */) inside a query was causing invalid test code.
64097	XML-related packages are no longer validated after install/upgrade, to avoid "ghost" warnings when XMLDB is not installed.
64327	Generated code contains lines like "l_fp_value ;" causing compilation errors.
64299	Single value queries containing single quotes cause errors when opened in Test Builder or Test Editor.
64363	Report contents for elements in test hierarchy below unit test are missing.
64493	Bulk insert of results data sometimes raising errors. Switched to row by row inserts.
64573	Override values for program and test code owners in import page are ignored for legacy (.qut) imports.
64577	ORA-06502 Bulk Bind: Truncated Bind errors occurring during code generation and display of code in Test Editor. Solution: switch from BULK COLLECT to cursor FOR loop. Impact: slower performance on 9.2.
64626	Suite level results are not exported to the XML documents. Import of this suite then raises an exception.
64573	Override values for program and test code owner are ignored for legacy (QUT) export files that have static/hard-coded schema names in the export file.
64577	ORA-06502: PL/SQL: numeric or value error: Bulk Bind: Truncated Bind occurs when trying to generate/then display in Test Editor, on Oracle9.2 only.
64626	Suite-level results are not included in XML exports.
64639	If the command line specification of a file contains odd characters like non-straight quotes or in any other way does not specify a valid file name for IMPORT, the import fails but no error is indicated.
64734	Incomplete test definition reports show no contents.
64757	Create a new test case in Test Builder and make it immediately inactive, then when you try to save, you get an unhandled exception from qu_harness in the validation process.
64852	XML import with code coverage data fails due to missing group tag plus failure on LINE# column handling in XML.
64907	Incomplete and Test Coverage reports for "all code" in selected or current schemas show report information repeatedly.
64909	All Programs in All Schemas with Tests Defined report shows all program units, not just those with tests defined.
64941	View Install log on Windows Vista has issue.
65000	Notify Support Bundle on Installation Wizard error.
65002	QU_REPORTS (PACKAGE BODY) is not valid on Oracle 9i2.
65040	Test builder should display warning message if the user does not have DBMS_PROFILER
65085	Licensing box does not display version of executable properly
65103	BOOLEAN expression outcome issue.

Known Issues

The following known issues existed at the time of this release:

Issue	Description
Generate Outcomes incorrectly saves NULL values	If you use the Generate Outcomes wizard and a calculated value is NULL, it will by default be displayed as a string "{null}", and this will be saved into the outcome as the expected value. You will need to manually change this string to a real NULL value before running your test to get a correct result.
ALTER SESSION commands in your code could cause errors	If you include statements like those shown below in your programs: EXECUTE IMMEDIATE 'ALTER SESSION SET NLS_SORT=BINARY_CI'; EXECUTE IMMEDIATE 'ALTER SESSION SET NLS_COMP=LINGUISTIC'; Then you will get runtime errors when you try to run your test.
Test definitions with expressions or single value queries may fail to run first time	If your test definitions contains outcomes for expressions or single value queries, then after importing you may get compile errors in your test code the first time you try to run the test. Errors will look like this: PLS-00103: Encountered the symbol ";" and the test code will contains lines of code like: l_fp_value ; (the datatype of the declaration is missing). In this case, simply open your test definition in Test Builder and immediately run your test. It should then compile without errors. After doing this, export your test definition and it should work properly after that point.
Formatting of test code now done on demand	In previous versions of Code Tester, the generated test package code was automatically formatted. For large tests, this step added too much time to the generation process. Now, the code will only be formatted if you open Test Editor, click on the Test Code tab and press the "Format and Compile" button.
Specification of table name in outcome may not contain a comment	When you specify the name of the table for a table outcome (for example: "Is a table empty?" or "Is this table equal to another table?"), you may not include any kind of comment next to the table name. Examples of invalid specifications of tables: EMPLOYEES /* employee table */ or EMPLOYEES – employees table.
Constraints on queries with unnamed expressions	If you test the contents of a query that contains unnamed expressions (that is, it is an expression rather than simply a column name and you do not provide a column alias), then that expression may not: contain a single quote, be equal to SYSDATE, or be equal to USER. Examples that will cause problems: SELECT name \|\| 'abc', SELECT SYSDATE, SELECT USER. This is due to idiosyncratic behavior in the Oracle parser.
Suite import does not notify user of missing programs	When you import a single test definition, Code Tester will warn you if it cannot find the program that this test definition purports to test. When you import a suite, this same warning will not be shown if one or more of the test definitions in the suite reference a program that cannot be found.
Problems with non-printing characters	Use of some non-printing characters, such as CHR(3) and CHR(4), in expressions and results can cause failures in the export/import process.
Merging of Test Definitions	Merging using the pre-1.8.3 technique of adding code to the .QUT export file will no longer work. Merging is only supported for XML export files.
Random number generation fails on Oracle9i	You will be unable to define test cases that rely on random number generation in Oracle9i. Limited support by Oracle for table function execution in SQL queries causes errors.
Cannot directly test a query	You cannot test a query directly. Instead, you will need to create a procedure that is, in essence, a "dummy" driver. Create a test definition for that procedure, then define an outcome for that query.
Cannot directly test a trigger	You cannot test a trigger directly. Instead, you will need to create and/or run a procedure that performs the DML operation necessary to fire the trigger. You then create outcomes to verify the changes made by the trigger.
Importing a suite	When you import a suite, it deletes any existing suite with the same name, even if it is actually a different suite owned by a different user.
Uninstalling a Code Tester Repository	When you uninstall a Code Tester repository, public synonyms are dropped, even if those synonyms are not owned by the schema from which you are uninstalling the repository. In this case, you will need to re-create the public synonyms.
Using a column named COLUMN_NAME	You cannot test the contents of a table or query with column named COLUMN_NAME. It must be renamed via the query's SELECT column alias.
Generate Outcomes hides errors	If your program raises an exception while using Generate Outcomes, that exception will not be shown to the user and no outcomes will be calculated/displayed.
Incorrectly interpreting the T/option	Prior versions of Code Tester incorrectly interpreted names in the /T option of command line execution as the names of tested programs, rather than the names of the test packages. Now, /T must list the name(s) of the test package(s). In other words, instead of /T=MYPKG, you would now write /T=Q##MYPKG.
32K Query Strings	Query strings of more than 32k are not supported.
Dataset Comparison Logic Containing Expressions	New dataset comparison logic does not work with a query that contains expressions that are not given column aliases.
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 should it start with OPEN FOR. It also should not have a terminating semi-colon. If you include such text, you may see compile errors in the generated test code or your query may be interpreted as a table name.
Unable to directly test object type methods	To test the method of an object type, you will have to create a wrapper for that program as a schema-level procedure or function, or within a package. You can then build a test definition for that wrapper program
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.
Testing the Contents of Cursor Variables	When testing the contents of cursor variables with very large numbers of rows, you may receive a "ORA-04030: out of process memory" error. This occurs because Quest Code Tester users nested tables to cache the cursor variable result set. You will need to reduce the number of rows analyzed in your test to avoid this issue.
Test data values consisting of very large strings	Test data values (values in Test Data Groups) cannot have more than 32,512 characters in them. While PL/SQL officially supports variable length strings of up to 32K (32767) characters, when using dynamic SQL the limit is reduced to 32,512. When working with Test Data Groups, Quest Code Tester applies those values using dynamic SQL, thus hitting the lower limit.
"Records Equal" function field names	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.
Tablespace Availability for Installation	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).
Import test definition to different schema	When you export a test definition, you can specify that you want the export owner set to the owner to which the test will be imported. This step will remove most but not necessarily all of the schema names in the test definition. Some may still be prefixed on packaged types, such as collection types and record types. This will cause compile errors on the test code. Solution: go into your test definition and change/remove those schema names, or edit the export file directly.
Specifying times for TIMESTAMP	You may not enter sub-second values in your timestamp value. Quest Code Tester only supports time specifications down to the nearest second.
Not connecting to ORACLE message	When adding customization logic to turns on DBMS profiling and running a test, you may encounter an ORA-03114: not connected to ORACLE message or an ORA-03113: end of file on communication channel error message and find that they have been disconnected from the database. This is an Oracle bug in the profiler logic and occurs inconsistently.
Object type inputs	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).

System Requirements

Before installing Quest Code Tester for Oracle, ensure your system meets the following minimum hardware and software requirements:

Platform	1.0 GHz x86 compatible CPU
Memory	512 MB of RAM recommended
Hard Disk Space	40 MB of disk space for installation
Operating System	Microsoft®Windows® 2000, 2003, XP Professional, Vista
Database/Client Versions	Database Server: Oracle 9i Database Release 2 (9.2.0.6 or above), Oracle Database 10g, Oracle Express Edition, and Oracle Database 11g Release Database Client: Oracle SQL Net 9, 10 and 11, plus Instant Client. For Oracle 64bit servers, 32bit client is required.
Required Database Privileges	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.

Global Operations

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release supports any single-byte character set. Double-byte or multi-byte character sets are not supported. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe.

Getting Started

Contents of the Release Package

The Quest Code Tester for Oracle release package contains the following items:

Quest Code Tester for Oracle version 1.8.4.
Product Documentation, including:
a. Online Help

b. Release notes

For More Information

Contacting Quest Software:

Email	info@quest.com
Mail	Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA
Web	http://www.quest.com

Refer to our Web site for regional and international office information.

Contact Quest Support:

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract.
Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com.

From SupportLink, you can do the following:

Quickly find thousands of solutions (Knowledgebase articles/documents).
Download patches and upgrades.
Seek help from a Support engineer.
Log and update your case, and check its status.

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.
The guide is available at: http://support.quest.com/pdfs/Global Support Guide.pdf.

This document contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.

Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, Knowledge Xpert, LeccoTech, LiteSpeed, LiveReorg, Matrix Insight, Matrix.Net, MIQ, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.

If you have any questions regarding your potential use of this material, contact:

Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656
Email: legal@quest.com

Disclaimer

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.