Query String Parameters not saving in exported Test Suite
POST Query String Parameters are not saving in exported Test Suite so that if I update my wadl and import the test suite my parameters are missing.
I have a test case where I needed to create my own query string parameters for a multipart/form-data Media request type, because it is a FormDataParam RESTful request type.
The Style and Level for each new parameter are the default (Query and Resource). I have set them both as a 'Required Parameters' and they are both strings.
When I export this test suite to be saved in subversion I can see that these parameters are saved in the xml, but when I import this test suite after updating the wadl (by removing it and adding the latest version of the wadl back to my project) I lose these parameters.
These parameters are being saved at the project level or directly on the wadl somehow and are not specific to the test suite. With how often we need to update the wadl in our projects this is not very efficient because we will need to recreate this test case from the new request in the wadl everytime we need to update the wadl (since there are no options to add parameters to a test case). But simply recreating this test case every time is not reasonable when we are trying to automated hundreds of tests.
This is a great feature in 4.6, but it would be a whole lot better if these parameters could be managed and saved at the test case level. From what we can tell, this type of request could not have been ran on soapUI 4.5.
Let me know if you need more information.
I have a test case where I needed to create my own query string parameters for a multipart/form-data Media request type, because it is a FormDataParam RESTful request type.
The Style and Level for each new parameter are the default (Query and Resource). I have set them both as a 'Required Parameters' and they are both strings.
When I export this test suite to be saved in subversion I can see that these parameters are saved in the xml, but when I import this test suite after updating the wadl (by removing it and adding the latest version of the wadl back to my project) I lose these parameters.
These parameters are being saved at the project level or directly on the wadl somehow and are not specific to the test suite. With how often we need to update the wadl in our projects this is not very efficient because we will need to recreate this test case from the new request in the wadl everytime we need to update the wadl (since there are no options to add parameters to a test case). But simply recreating this test case every time is not reasonable when we are trying to automated hundreds of tests.
This is a great feature in 4.6, but it would be a whole lot better if these parameters could be managed and saved at the test case level. From what we can tell, this type of request could not have been ran on soapUI 4.5.
Let me know if you need more information.
