+++ Step 1 Create a duplicate registry entry for the application to be tested with TEST appended to the IVORN - so for example, ivo://org.astrogrid/sextractor would be duplicated as ivo://org.astrogrid/sextractorTEST (the actual registry entries should be the same apart from the ivorn).

NOTE: These test entries already exist for many applications (e.g. look in the galahad registry to view the two entries mentioned above).

+++ Step 2 Edit the TEST entry so that it has "status=inactive" (rather than "status=active" as the real entry has). This means that workflows can still use the test entry, but it won't show up in the GUI as a tool choice.

+++ Step 3 Configure your CEA such that it runs the application under test using the TEST ivorn rather than the real one, in the CEAApplicationConfig^?.xml file (or whatever you've called this file). ALSO, edit the registry entry for your CEA so that it offers the TEST ivorn as a service, rather than the real one.

+++ Step 4 Edit a workflow that runs the tool (by hand) so that it refers to the TEST application entry (e.g. ivo://org.astrogrid/sextractorTEST) rather than the real one. Test your application and CEA using this workflow until you're happy they are working.

+++ Step 5 Reconfigure your (now working) CEA to refer to the REAL application entry (e.g. ivo://org.astrogrid/sextractor) rather than the real one, and change the registry entry accordingly. You're done!

-- KonaAndrews - 31 Aug 2005