Kathryn_O_Malle
16 years agoContributor
Saving testsuite properties between external execution runs
Hi there,
Bit of an oddball question this one...
In our system testing we execute SoapUI testsuites / testcases as required externally via a third party automation tool. In this case Rational Functional Tester (RFT)v8.x. Each time we execute SoapUI via Java (RFT scripting language).
We pass parameters down to SoapUI and these are used to update testsuite / testcase properties as required. But when each SoapUI execution completes these updated testsuite / testcase properties have not been saved to SoapUI. Thus the next SoapUI is called the original testsuite / testcase properties are there instead.
Is there a way, say an SoapUI API call made before the SoapUI execution completes, to ensure the latest testsuite / testcase properties are saved to disk???
Many thanks
Adam Hall
[NB: Currently using SoapUI 3.01 with our project work...]
Bit of an oddball question this one...
In our system testing we execute SoapUI testsuites / testcases as required externally via a third party automation tool. In this case Rational Functional Tester (RFT)v8.x. Each time we execute SoapUI via Java (RFT scripting language).
We pass parameters down to SoapUI and these are used to update testsuite / testcase properties as required. But when each SoapUI execution completes these updated testsuite / testcase properties have not been saved to SoapUI. Thus the next SoapUI is called the original testsuite / testcase properties are there instead.
Is there a way, say an SoapUI API call made before the SoapUI execution completes, to ensure the latest testsuite / testcase properties are saved to disk???
Many thanks
Adam Hall
[NB: Currently using SoapUI 3.01 with our project work...]