Toad World® Forums

What to do with test definitions created in different schemas, instances?


#1

A user recently asked me:

What happens if we create a testcases of a different functions, procedures, package functions in the same schema,
but on a different databases and then we import them all on the same schema on one database,
could anything in database be overrriten, is there a risk that this could cause problems for CT ?
For ex.:
- in schema JOHN on database DB1, in CT was created test case for package function DEP_DOC.INSERT_DOC,
- in schema JOHN on database DB1, in CT was created test case for package function DEP_CLOSE_ADD.FUNCTION_TEST,
- in schema JOHN on database DB2, in CT was created test case for package function DEP_CLOSE.START_CLOSE,
- in schema JOHN on database DB2, in CT was created test case for package function DEP_CLOSE.COUNT_TAX,
- in schema JOHN on database DB3, in CT was created test case for package function DEP_DOC.CANCEL_PACK,
and so on and so fourth…
then we export all testcases from all databases and we import them on database DB_REPOSITORY.


#2

You can have only one test definition for a given program in a schema. So if you simply import test definitions for the same program into the same schema (originally defined in different instances), you can overwrite tests.

However, we currently support the merge of test definitions. This merge process must be specified through backend API programs and thus is a bit tricky. Make sure that you keep backups of all your test definitions, preferably even an Oracle export of the Code Tester schema (in addition to the CT export files), before trying the merge process.

You should also read through the Release 1.8 (currently in beta, available in production in March) Help document’s Troubleshooting section on Export/Import, as we have identified a number of issues for this process that you may need to resolve before the merging.