lanahorton
12 years agoOccasional Contributor
Time out issues
I tried using SoapUI LoadTest and found that because my test cases contain several transfers, it's not suitable.
I'm hoping LoadUI might be able to handle the transfers in a more efficient way.
Here is the scenario...
DataGen - generates unique requestID
Properties - repository for new on-the-fly data
Step 1 - a script runs and a unique value is created
Step 2, transfer - the unique value is saved in the Properties file - some test cases contain more than one transfer - Typical transfer: declare namespace ns1='https://${#TestSuite#Endpointall}/xxxxxxxx/2013/09/10/xxxxxxxxSms';
//ns1:Response[1]/ns1:Response[1]/ns1:xxxxxxxxxxxxxId[1]
Step 3, get - a script that accesses Properties for an SMS Pin executes
Step 4 - SMS Pin is transferred ( //smspin[1] )
The problem with SoapUI LoadTest is that even when delays are added to the test cases, values such as Pin numbers are being stepped all over. I can run one single thread one time for a pass, but no actual load testing.
The dilemma is two-fold -
1) will LoadUI be able to handle these requests without becoming confused with multiple threads?
2) since my trial license expired before my boss returned to me for information on the LoadUI evaluation (where I ran send/receive scripts rather than one like described above), is it possible to get another or to extend the one I have?
I'm hoping LoadUI might be able to handle the transfers in a more efficient way.
Here is the scenario...
DataGen - generates unique requestID
Properties - repository for new on-the-fly data
Step 1 - a script runs and a unique value is created
Step 2, transfer - the unique value is saved in the Properties file - some test cases contain more than one transfer - Typical transfer: declare namespace ns1='https://${#TestSuite#Endpointall}/xxxxxxxx/2013/09/10/xxxxxxxxSms';
//ns1:Response[1]/ns1:Response[1]/ns1:xxxxxxxxxxxxxId[1]
Step 3, get - a script that accesses Properties for an SMS Pin executes
Step 4 - SMS Pin is transferred ( //smspin[1] )
The problem with SoapUI LoadTest is that even when delays are added to the test cases, values such as Pin numbers are being stepped all over. I can run one single thread one time for a pass, but no actual load testing.
The dilemma is two-fold -
1) will LoadUI be able to handle these requests without becoming confused with multiple threads?
2) since my trial license expired before my boss returned to me for information on the LoadUI evaluation (where I ran send/receive scripts rather than one like described above), is it possible to get another or to extend the one I have?