Forum Discussion
eeyoreeco
11 years agoOccasional Contributor
PaulM wrote:
eeyoreeco wrote:
PaulM wrote: This is a server side issue. Essentially, your dev team would have to create this. The problem is, why? If it continues to parse a request that it knows is faulty than it is wasting processing speed. Which in turn costs more money.
Actually the reason why I'm asking this, so that in just one run of 'request' I will be able to verify all the validation for all parameters that are in the xml request. (for testing purposes - negative scenario)
Yes, I understand that this would make testing far easier but as I said, it would require development to change the code to continue parsing the data after invalid data is found on the server side. While this would be amazing for testing purposes in production this would be horrible since it will consume all of the standard resources that a failed example would consume.
If you want development to make a change that will hinder production and cost your company FAR more money just to make testing easier. Instead of wanting that, why not set up a groovy script that will constantly replace a single node with a faulty parameter and then run the test case over and over again to verify the failures?
Thanks Paul!. would you be able to help me regarding of using a groovy script that will constantly replace a single node with a faulty parameter and then run the test case over and over again ?