Ran into the following problems after Quest Code Tester was installed. The program started up fine and then Edit | New Test Definition is selected.
1. Owner selected:UserName
2. Package selected: SOME_PKG
(valid status, etc)
3. Clicked OK
ORA-01400: cannot insert NULL into ()
ORA-06512: at JSMITH.QU_RUNTIME, line 1426
ORA-06512: at JSMITH.QU_RUNTIME, line 1449
ORA-06512: at JSMITH.QU_RUNTIME, line 1545
ORA-06512: at JSMITH.QU_HARNESS_CP, line 350
ORA-01400: cannot insert NULL into (JSMITH.QU HARNESS.HARNESS OWNER)
ORA-06512: at JSMITH.QU_HARNESS_CP, line 575
ORA-06512: at line 4
HANDLE_ERROR_IN boolean := sys.diutil.int_to_bool(:HANDLE_ERROR_IN);
( UNIVERSAL_ID_IN => :UNIVERSAL_ID_IN, HARNESS_OWNER_IN => :HARNESS_OWNER_IN, NAME_IN => :NAME_IN <...etc...> );
Set up to login withUserName as OS authentication. Usually login as username/password --> EXTERNAL/
OS Authentication requires that you log in with NULL fields in initial connection. QCTO is trying to use the invalid parameter of NULL, and ends up erroring out.
Connect with database identification.
This issue is fixed in Code Tester for Oracle 1.6.1. The latest version of Code Tester for Oracle can be downloaded here.