SOAP XPath Match Assertion in Load Tests?
Hello,
I am fairly new to SOAP UI Pro. I have no scripting ability but I do have resource for this should my aims require such measures !
My aim is to create a set of load tests through SOAP UI Pro which each have an XPath Match assertion to ensure that the responses received for the SOAP requests do not contain errors (by errors I mean application errors).
The assertion which I have applied within each step (i.e. not a seperate test step):
My load test when created contains
1. Data Retrieval
2. SOAP Request Type 1
3. SOAP Request Type 2
..
10. SOAP Request Type 10
After realising that the assertion is not applied within the load test and that the only assertions I can add within the load tests are load test assertations, I decided to try out the Add Assertion Test Step. I added a single assertion test step, like the example in quotes, where the source was SOAP Request Type 1 and Property set to Response to see what would happen. The assertion test step message insolation starts with and still remains at UNKNOWN which I think is quite strange, even after re-runing the SOAP Request Type 1 step. Please note that the assertation in quotes was derived directly from an earlier response, and the re-run of the request I have conducted is the same request with the same parameters. Therefore is should be VALID.
I decided to proceed to see what would happen in the load test as I can now see that the test step has been included automatically within the load test suite. However when I run the load test, the assertion test step "fails". There is no reason given apart from XPath Match FAILED - I can't tell if this means the xpath itself has failed or is it due to a similar reason that the assertion test step in isolation remains at UNKNOWN. However as noted before I know that it should not be failing.
So my first question is what am I doing wrong? Or rather, is there a better way of doing this?
Secondly, my aim is to identify which of the many requests have produced application failures, so I can omit these response times from my CSV exports so that they do not skew my results. Is there a way I can do this?
I would greatly appreciate if anyone could point me in the direction to any materal online that may help me with this or suggest anything here.
Regards
Kyle
I am fairly new to SOAP UI Pro. I have no scripting ability but I do have resource for this should my aims require such measures !
My aim is to create a set of load tests through SOAP UI Pro which each have an XPath Match assertion to ensure that the responses received for the SOAP requests do not contain errors (by errors I mean application errors).
The assertion which I have applied within each step (i.e. not a seperate test step):
declare namespace ns0='http://tempuri.org/';
//ns0:ExecuteResponse[1]/ns0:ExecuteResult[1]/ns0:ResponseMethod[1]/ns0:ResponseResult[1]/ns0:ExtendedDetail[1]
Expected Result:
No Error
My load test when created contains
1. Data Retrieval
2. SOAP Request Type 1
3. SOAP Request Type 2
..
10. SOAP Request Type 10
After realising that the assertion is not applied within the load test and that the only assertions I can add within the load tests are load test assertations, I decided to try out the Add Assertion Test Step. I added a single assertion test step, like the example in quotes, where the source was SOAP Request Type 1 and Property set to Response to see what would happen. The assertion test step message insolation starts with and still remains at UNKNOWN which I think is quite strange, even after re-runing the SOAP Request Type 1 step. Please note that the assertation in quotes was derived directly from an earlier response, and the re-run of the request I have conducted is the same request with the same parameters. Therefore is should be VALID.
I decided to proceed to see what would happen in the load test as I can now see that the test step has been included automatically within the load test suite. However when I run the load test, the assertion test step "fails". There is no reason given apart from XPath Match FAILED - I can't tell if this means the xpath itself has failed or is it due to a similar reason that the assertion test step in isolation remains at UNKNOWN. However as noted before I know that it should not be failing.
So my first question is what am I doing wrong? Or rather, is there a better way of doing this?
Secondly, my aim is to identify which of the many requests have produced application failures, so I can omit these response times from my CSV exports so that they do not skew my results. Is there a way I can do this?
I would greatly appreciate if anyone could point me in the direction to any materal online that may help me with this or suggest anything here.
Regards
Kyle