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

What sort of assertions are you using to process the test and verify it passes? 

I perform an xPath Match assertion to count the values of a tag matching a specific value based on project variables.  Normally this isn't a problem, but when the line sizes get beyond 10000 I've had it lock up SoapUI and the only resolution is to kill the process and start over.  I've let it run for 20-30 min.before doing so.

The issue is in order to confirm the values it needs to read all the XML.  I wouldn't think this is an unusual request. 

I'm not a novice but I'm not an expert either.  Below is my assertion, can you see a better way to do this assert?

declare namespace ns1='http://xxx.org/';
declare namespace a='http://xxxxx.V3.ServiceTypes';
(count(//a:Coverages[1]/a:Coverage/a:Form/a:Name[text() = "${#TestSuite#FormName13}"]) = count(//a:Coverages[1]/a:Coverage/a:Form/a:Name))
and
(count(//a:Coverages[1]/a:Coverage/a:Form/a:Name)>0)

The first part:  Counts the possible form names, every coverage MUST have a form name.  So if there is only one kind of form name then every coverage should be accounted for.  Sometimes there is more than one and I take that into account.

The second part:  confirms there are coverages, otherwise it should fail.

Would it be better to split these up into separate assertions? I'm not convinced this wouldn't be a problem still.

Thanks for any advice!

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!

So the form name can be 1 or more form names that I'm comparing.  So lets change the scenario and say I have 3 different form name property/variables: name1, name2 and name3.  Also lets say my form's count (counting up all the xpath form/names) is 50 (as an example). 

I'm totaling up count(name1) + count(name2) + count(name3) to make sure all the form/name combinations are accounted for.  So checking if it's equal to the overall xpath form/names count confirms this.  I couldn't think of a better way to make sure all my tags have a value and a correct value.

I was trying to keep my example simple, but the assertion can get a little more complex.  I'm wondering if the better fix would be to split the 2 checks into 2 separate assertions?  Put the if count>0 in one assertion and then verify all the other sums of form name counts in another assertion.  I just feel the latter will still have somewhat of an issue.

It's just odd the running of the test case or the testing inside the assertion runs quick.  But when I save out of editing it takes so long.

Thanks!