Laslow
12 years agoNew Contributor
Changed Response SLA wasn't saved in project xml
Hi,
I have set a Response SLA for a Test Request. Everything was OK. Later I changed it in the Configure Response SLA Assertion window, I clicked on OK, and I saved the project (right click on the project in the Navigator window, and Save Project).
The project xml file was saved because the file date was updated right but the SLA hasn't changed. I have searched it in the project xml under the con:assertion type="Response SLA Assertion" name="Response SLA" tag and there was the old value not the new one.
I have edited and saved it many times in soapUI, and the date of the project xml file was every time updated but the Response SLA stayed the same. After about a dozen tries once the Response SLA was also saved, and since that time it works well.
I have no idea why it hasn't saved the new Response SLA so many times. Now it works perfectly and I don't know what the problem was. Unfortunately I have no copy of the xml version with the not changing Response SLA so I can't compare it to the current one.
I have set a Response SLA for a Test Request. Everything was OK. Later I changed it in the Configure Response SLA Assertion window, I clicked on OK, and I saved the project (right click on the project in the Navigator window, and Save Project).
The project xml file was saved because the file date was updated right but the SLA hasn't changed. I have searched it in the project xml under the con:assertion type="Response SLA Assertion" name="Response SLA" tag and there was the old value not the new one.
I have edited and saved it many times in soapUI, and the date of the project xml file was every time updated but the Response SLA stayed the same. After about a dozen tries once the Response SLA was also saved, and since that time it works well.
I have no idea why it hasn't saved the new Response SLA so many times. Now it works perfectly and I don't know what the problem was. Unfortunately I have no copy of the xml version with the not changing Response SLA so I can't compare it to the current one.