LZhang
15 years agoFrequent Contributor
Beta 3.5 is not able to save requirement/test cases mapping
Hi:
I have encountered a problem in trying to save requirement mapping.
Steps to reproduce:
1. Get the latest from source control
2 check out and lock the settings.xml from the project level
3. Open the project in SoapUI and go to requirement tab --> map on eof the requirements to a few
test cases.
4. Save the project
5. Check in the settings.xml to source control
6. exit soapUI or reload the project and it shows that no test cases have been mapped to the requirement. Basically, my mapping
didn't get saved in SoapUI.
However, I found out that if I check out the entire test suite (where the test cases reside) as well as the settings.xml (at project level),
then the mapping will get saved correctly.
Is this a bug? The version of SoapUI that I am using is
Build daily-2010-01-25-[3], Build Date 2010/01/25 17:07
Thanks,
Li Zhang
I have encountered a problem in trying to save requirement mapping.
Steps to reproduce:
1. Get the latest from source control
2 check out and lock the settings.xml from the project level
3. Open the project in SoapUI and go to requirement tab --> map on eof the requirements to a few
test cases.
4. Save the project
5. Check in the settings.xml to source control
6. exit soapUI or reload the project and it shows that no test cases have been mapped to the requirement. Basically, my mapping
didn't get saved in SoapUI.
However, I found out that if I check out the entire test suite (where the test cases reside) as well as the settings.xml (at project level),
then the mapping will get saved correctly.
Is this a bug? The version of SoapUI that I am using is
Build daily-2010-01-25-[3], Build Date 2010/01/25 17:07
Thanks,
Li Zhang