I am using the VAPI-XP mechanism to invoke a specialised test harness via a web service, process the response, and post the result back into TD. It all works fine, but...
My VAPI-XP script gets all the variable information it needs from the three passed TD objects (TestSet, Test, Run). So the code for each VAPI-XP script is always the same.
But each VAPI-XP test I create offers me the option to name the script, then seems to ignore it and generates a new skeleton anyway. I don't want to create 300 identical scripts, I want to use the same script for all of them.
As an interim solution, I have moved all but two lines of my code out to a submodule, so at least I only have one copy of it. But I still get one VAPI-XP script per test.
One possibility is to have just one parameterised VAPI-XP test and associated script, and call it from all the other tests, just passing the parameter. But I can't seem to add a parameter to the VAPI-XP test. Has anyone else done anything similar?
I'm pretty new to TD, so it's possible I'm barking up the wrong tree entirely.
My VAPI-XP script gets all the variable information it needs from the three passed TD objects (TestSet, Test, Run). So the code for each VAPI-XP script is always the same.
But each VAPI-XP test I create offers me the option to name the script, then seems to ignore it and generates a new skeleton anyway. I don't want to create 300 identical scripts, I want to use the same script for all of them.
As an interim solution, I have moved all but two lines of my code out to a submodule, so at least I only have one copy of it. But I still get one VAPI-XP script per test.
One possibility is to have just one parameterised VAPI-XP test and associated script, and call it from all the other tests, just passing the parameter. But I can't seem to add a parameter to the VAPI-XP test. Has anyone else done anything similar?
I'm pretty new to TD, so it's possible I'm barking up the wrong tree entirely.