Forum Discussion
Elvorin
13 years agoContributor
I'm afraid that will not be possible. I cannot disclose the project. It'll be against company privacy policy. It's a large scale eCommerce platform project. Currently we are trying to test a particular service of it.
If you are looking for any particular information, please let me know, and I'll be glad to provide you that.
To give you an idea how we are setting up our project -
we set up test cases in SOAPUI. Test steps are very straightforward. It has a DataSource to read input from a comma separated file, next it makes a SOAP call for the service we wanna test. SOAP call has 2 assertions, SOAP Response and Not SOAP Fault. For every test case data source is shared and set for looping through during the load testing. Then we setup our LoadUI test case. There we get all these service calls as separate SOAPUI runner and attach these with generators (Fixed/Random) based on our requirement on call distribution. Also we attach the error out to a table log.
Above is our intended setup. But then we noticed on error, no useful information was getting logged to debug, like input/output etc. So I added properties to each of the test case in SOAPUI, added a property transfer step to populate them and then in SOAPUI Runner enabled the test case property logging and attached results output to another table log component. This is our current setup.
If you are looking for any particular information, please let me know, and I'll be glad to provide you that.
To give you an idea how we are setting up our project -
we set up test cases in SOAPUI. Test steps are very straightforward. It has a DataSource to read input from a comma separated file, next it makes a SOAP call for the service we wanna test. SOAP call has 2 assertions, SOAP Response and Not SOAP Fault. For every test case data source is shared and set for looping through during the load testing. Then we setup our LoadUI test case. There we get all these service calls as separate SOAPUI runner and attach these with generators (Fixed/Random) based on our requirement on call distribution. Also we attach the error out to a table log.
Above is our intended setup. But then we noticed on error, no useful information was getting logged to debug, like input/output etc. So I added properties to each of the test case in SOAPUI, added a property transfer step to populate them and then in SOAPUI Runner enabled the test case property logging and attached results output to another table log component. This is our current setup.
Related Content
- 11 months ago
- 2 years ago
Recent Discussions
- 2 days ago