Ask a Question

Exclude Certain Steps from LoadTest Statistical Calculation in SoapUI Pro

JMalvin
Occasional Contributor

Exclude Certain Steps from LoadTest Statistical Calculation in SoapUI Pro

We have a mix of JDBC and service request steps in our test cases. I was wondering if we can have the statistical numbers only include the service requests so it won't affect TPS (transaction per second), and have JDBC steps excluded? We would still wish to run the JDBC to validate the assertions in the service request steps but just not include them as a part of the statistical calculation.

 

Is there a way to accomplish this?

5 REPLIES 5
nmrao
Community Hero

Are you running the load test from SoapUI NG? Disabling the step temporarily and enable it later while doing functional tests works?


Regards,
Rao.
JMalvin
Occasional Contributor

No, we are running the load test in SoapUI Pro.

 

And, yes, we can temporarily disable JDBC steps and run the services, but there are two issues with that approach:

 

  1. There are a few dozen JDBC steps for some of these test cases. Enabling and disabling them is a daunting process which should be avoided.
  2. There are a few hundred assertions that depend on responses coming back from JDBC steps. Disabling the latter steps would result in stream of these failed assertions.

 

I just need the load test calculation to ignore certain steps if possible and not to take them into consideration.

nmrao
Community Hero

On the whole if you can disable the jdbc steps it is enough. If step is disabled, then there is no question of assertion associated to it, right?


Regards,
Rao.
nmrao
Community Hero

And do you have any certain pattern for the jdbc step name? So that it is can easily be identified to disable.


Regards,
Rao.
JMalvin
Occasional Contributor

I understand that if one to disable JDBC steps, the TPS values would correctly represent the service requests' throughput. However, the "err" columns then would lid up as all the assertions that match values between JDBC returned rows and Soap response fail which is not something I would like to show in the reports.

 

I tried to run all the steps, then disable the JDBC steps and execute the load test, hoping that the records retrieved through this "manual" run would persist, and can be used in the load test. But, alas, the load test simply ignores them.

 

P.S. JDBC steps have been marked distinctively, so identifying and disabling them is of no issue.

cancel
Showing results for 
Search instead for 
Did you mean: