One of our priorities for upcoming releases of Code Tester is to automate the process of code evolution (new arguments, changed names, etc.). Today, you must make manual changes for the most part to adapt existing test definitions to changes in programs.
As for your particular change…I am going to give you a quick piece of advice, and then think about it some more (and possibly come up with a better answer):
What you should do immediately is create the package with the program, and then modify the procedure to simply be a “pass through” to call the packaged program.
Leave the test definition as is.
This is obviously sub-optimal, but that may be the best/simplest we can offer right now. Hopefully more soon…