"Automating" Unit Test Deployment

Question

We're trying to develop an automated build process using SQL Developer's Unit Test. This works by developing the unit test(s) on database A and then deploying the unit test(s) to database B for the build. Unfortunately, there is an issue when we come to import a new version (v2) of an existing test (v1). If a previous version of the test already exists on database B then the old version is sometimes merged with the new version.
A simple example would be where:
(v1) Version 01 has a Startup Process but no Teardown Process
(v2) Version 02 has a Teardown Process but no Startup Process
If I import Version 01 then Version 02 I get a test with both a Startup Process and a Teardown Process
Now, we've managed to manually work around this by using the command - Purge Repository Objects; but this is not ideal as the process is meant to be fully automated.
Any Ideas...

Answer 1

Phillip / Brian
Is it possible to "Purge Repository Objects" through a SQL script instead ?
From what I can infer from looking at the UT tables the "Purge" truncates all the UT tables except UT_LOOKUP_CATEGORIES and UT_METADATA. Now, I've tried this but it doesn't quite seem to work. I'm missing something here.
I get the following error message when I try to import files after my manual "purge":
ORA-01400: cannot insert NULL into ("DCI_UT_REPO"."UT_TEST"."CREATED_ON")
01400.00000 - "cannot insert NULL into (%s)"
Regards
Subboss