Forum Discussion

khanchett's avatar
khanchett
Contributor
7 years ago

When doing an assert on a large response (10,000-50,000 lines) SoapUI is taking a long time 5+mins.

I have a response that is anywhere between 10,000 and 50,000 lines.  I have a few asserts that check the uniqueness of those values.  I understand this will take some time, but is there anyway to des...
assertion
SoapUI
  • groovyguy's avatar
    groovyguy
    7 years ago

    The groovy script I provided can be easily adapted to check against multiple expected form names. To address your latest concern, I have noticed the same behavior. Whenever you edit/change a groovy script assertion and close the window, it reprocesses that assertion and re-runs it against the response. There's no real way around that unfortunately. I am not sure why it would take so much longer. 

khanchett's avatar
khanchett
Contributor

So here is something interesting.  When the test runs those assertions don't take as long as if I edit the assertion after a run. 

 

I updated the previous assertion to groovy and it still takes a really long time after an edit.

 

def groovyUtils = new com.eviware.soapui.support.GroovyUtils(context)
def responseHolder = groovyUtils.getXmlHolder(messageExchange.responseContent)
Boolean flag = true;

// Count all form name tags
int formNamesCount = Integer.parseInt(responseHolder.getNodeValue("count(//a:Coverages[1]/a:Coverage/a:Form/a:Name)"))

//Count all the forms with a match to give names from relevant test suite property 
def formName = context.expand( '${#TestSuite#FormName3}' )
int formNamesCount2 = Integer.parseInt(responseHolder.getNodeValue("count(//a:Coverages[1]/a:Coverage/a:Form/a:Name[text() ='" + formName + "'])"))
if((formNamesCount != formNamesCount2) ||  (formNamesCount<=0)){
	flag = false
}
assert flag

So the steps to recreate this is the following:

  1. I run my test step, this will execute all the assertions that I have and it doesn't take super long.
  2. I find the one assert to change based on something I see in the response to update.
  3. I open the XPath Match or, now updated, Script Assertion.
  4. I edit whatever and click the test button, it responds quickly.
  5. Now when I do one or the other I get the long delay.
    1. XPath Match - clicking SAVE it will hang the screen until it's finished.
    2. Script Assertion - clicking OK it will return to the Assertions listing but SoapUI is completly locked until it's finished.

So the main question is what is different from the run or clicking the test button, to the actual saving of the assertion, whichever it is.

 

Hopefully this explains the issue best.  I was hoping the Groovy script was the answer. 

 

If you see anything in the code I can change to improve it I'm all ears.  :smileywink:  I appreciate all the feedback!

 

Thanks!

 

groovyguy's avatar
groovyguy
Community Hero
7 years ago

I am going to build off of your groovy script a little bit and see if I can help. Looking at your script, you are still counting everything nultiple times, which still duplicates your effort. 

 

def groovyUtils = new com.eviware.soapui.support.GroovyUtils(context)
def responseHolder = groovyUtils.getXmlHolder(messageExchange.responseContentAsXml)
Boolean flag = true;

// Count all form name tags
int formNamesCount = responseHolder["count(//a:Coverages[1]/a:Coverage/a:Form/a:Name)"].toInteger();

// Get all form name tags
def formNames = responseHolder["//a:Coverages[1]/a:Coverage/a:Form/a:Name"]

def formName = context.expand( '${#TestSuite#FormName3}' )

// Test if there is only one object in response
if (formNamesCount == 1)
{
	// Only one formName returned
	assert (formNames.equals(formName)
}
else if (formNamesCount > 1)
{
	// More than one formName returned
	assert (formNames.count{ it.equals(formName) } == formNamesCount)
}
else 
{
	// Zero items returned condition
	// Handle this as you wish, I usually assume a failure as I expect data returned
	assert false;
}