Forum Discussion
PerfTestMike
15 years agoContributor
OK, so update time!
As an alternative to exporting your test from SoapUI to LoadUI, what you can do is:
1) Create your test in SoapUI;
2) recreate it in LoadUI manually;
3) save script in C:\Program Files\Eviware\LoadUI\Script Components;
4) manually recreate your test using the attached CSV reader (created for standard CSV use which takes the first row as the field name and the following rows underneathe as the corresponding values);
4a) Place this element between the load generator and the soapUI runner;
The advantage of this is that it removes the user from any test-exporting related issues (as I've found my tests have corrupted after exporting from SoapUI to LoadUI). It should mean you can create a test without having to mess about with setting up data in soapUI
As an alternative to exporting your test from SoapUI to LoadUI, what you can do is:
1) Create your test in SoapUI;
2) recreate it in LoadUI manually;
3) save script in C:\Program Files\Eviware\LoadUI\Script Components;
4) manually recreate your test using the attached CSV reader (created for standard CSV use which takes the first row as the field name and the following rows underneathe as the corresponding values);
4a) Place this element between the load generator and the soapUI runner;
The advantage of this is that it removes the user from any test-exporting related issues (as I've found my tests have corrupted after exporting from SoapUI to LoadUI). It should mean you can create a test without having to mess about with setting up data in soapUI
