Forum Discussion
mkalboneh
12 years agoOccasional Contributor
Thank you for the reply nmrao,
I can't provide exact xml because it's for work. What I can do is describe the flow:
I have a soap UI test that consist of the following steps:
1- "Add Cars" step will send an add cars request, then come back with a response with IDs for the cars added
2- Groovy step that extract those IDs from the first step response, then append them to the next step request
3- This step will call with Car IDs to verify that cars were added
Now, I would like to run those steps over and over for load testing purposes. The problem is:
That request for the third step (verification) where I am appending the IDs, still contain the IDs from the last time it ran.
I need to add to the groovy script in step 2, so it checks and deletes all existing car IDs in the third step request, so they won't be sent again for verification.
So every time that third step will run, it only contains IDs for cars that were just added during this run.
The xml provided is just an example, but it does describe my end goal here.
So, I would like to be able to remove those nodes iteratively throughout the whole request before appending the new ones.
I hope this helps a little answer my question.
Thanks You!
I can't provide exact xml because it's for work. What I can do is describe the flow:
I have a soap UI test that consist of the following steps:
1- "Add Cars" step will send an add cars request, then come back with a response with IDs for the cars added
2- Groovy step that extract those IDs from the first step response, then append them to the next step request
3- This step will call with Car IDs to verify that cars were added
Now, I would like to run those steps over and over for load testing purposes. The problem is:
That request for the third step (verification) where I am appending the IDs, still contain the IDs from the last time it ran.
I need to add to the groovy script in step 2, so it checks and deletes all existing car IDs in the third step request, so they won't be sent again for verification.
So every time that third step will run, it only contains IDs for cars that were just added during this run.
The xml provided is just an example, but it does describe my end goal here.
So, I would like to be able to remove those nodes iteratively throughout the whole request before appending the new ones.
<ns:color></ns:color>
I hope this helps a little answer my question.
Thanks You!
Related Content
- 2 years ago
- 4 years ago
- 2 years ago
Recent Discussions
- 15 years ago