ContributionsMost RecentMost LikesSolutionsEnable select all for assertions in requestHi: Current version of soapUI doesn't enable "select all" for deleting assertions. We have some test cases in which there are like 30+ assertions for a request. We have to manually select each one of them to remove which is very time consuming. Adding a feature to be able to select a number of assertions to remove is highly desirable. Thanks, Li ZhangRe: resolve target/source properties in one clickHi: Can this feature be added to the newest release of soapUI as it really doesn't make sense to go though hundreds of steps to resolve them one by one? Regards, Li ZhangRe: Beta 3.5 is not able to save requirement/test cases mappingHi: I tried tracing the content in settings.xml (on the project level) before and after but didn't notice anything differences. Here is what I suspect, if you CLONE a test case from another project to your composite project, then map this test case to your requirement and save all. Don't use ctrl-s, would you be able to reproduce it? Not sure if it has anything to do with cloning a test case. Thanks, Li ZhangRe: Beta 3.5 is not able to save requirement/test cases mappingI tried both ways by clicking the "save all projects" as well as right clicking on the project and explicitly saving it. Made no difference. LiRe: Beta 3.5 is not able to save requirement/test cases mappingJust want to re-iterate what I noted in my initial thread that if I checked out the ENTIRE test suite for which I wanted to map the requirement to, the requirement would indeed get saved. So it's worthwhile investigating the settings.xml INSIDE the test suite folder. It might have impact on the overall project level requirement mapping. LiRe: Beta 3.5 is not able to save requirement/test cases mappingHi: Do you think it might due to the fact that the test cases I wanted to map to were cloned from existing project? I have attached the project that I am working on. If you can open it and go to requirement tab --> map the last requirement 5424 to test cases in Product-Back-Log-Project --> 5424-EU-Testing suite --> select all test cases. What I did was I saved the project after mapping and checked it into TFS and then reloaded the project. Evidently, the mapping was gone in requirement. Is it possible for you to clone your test cases and map them to a requirement and try to save and check it into source control and see if you can reproduce the issue? Thanks, Li ZhangRe: Have soapUI hot load the settings.xml file or force the user to reload a projectBasically, soapui should do the same behavior as it does for groovy. Maybe for setting.xml, soapui can suggest merge if a newer file was downloaded because of tfs sync ?Re: Beta 3.5 is not able to save requirement/test cases mappingHi: Any follow-up or update on this? Thanks, LiHave soapUI hot load the settings.xml file or force the user to reload a projectHi: Is it possible to have soapUI hot load external changes to the settings.xml file in a composite project as we have encountered many incidents such that when user 1 makes in a change to a composite project and checks it into source control, and now user 2 gets the latest and checks it out to lock the project. However user 2 forgets to reload the project after checking it out on his local machine, then he goes on making changes and checks it back to source control. What happen is the changes user 1 makes will be overwritten by user 2. Therefore, if soapUI hot loads the external changes to settings.xml or forces a user to RELOAD his project, then changes from a previous user won't be overwritten. Thanks, Li ZhangBeta 3.5 is not able to save requirement/test cases mappingHi: 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