Forum Discussion
Mason
15 years agoFrequent Contributor
Everyone is on the 05/18 build but I still see messages in the log indicating certain test cases that I did not modify are being saved.
Part of my original question was how are users supposed to save their work? At what level? And with what command? For example, what is the Composite Action -> Save Test Case for? Is this how people within a composite project are supposed to save their work? Or is a user supposed to be able to right-click on the project and then click "Save Project" and SoapUI determines what aspects of the project were modified and only saves those changes? There are no log messages when performing the Composite Action - > Save Test Case. So I'm not sure what that does, if anything.
The documentation doesn't really explain "how" multiple users are supposed to behave within a composite project. If Eviware could elaborate on that, I think it would be most helpful in troubleshooting these inconsistencies. We, as users, may very well be doing something the product is allowing us to do but is not intended.
Also, I'm curious as to why there is not a "Save Suite" Composite Action? Having to save all of the test cases in a suite can get a bit time-consuming.
Thanks.
Part of my original question was how are users supposed to save their work? At what level? And with what command? For example, what is the Composite Action -> Save Test Case for? Is this how people within a composite project are supposed to save their work? Or is a user supposed to be able to right-click on the project and then click "Save Project" and SoapUI determines what aspects of the project were modified and only saves those changes? There are no log messages when performing the Composite Action - > Save Test Case. So I'm not sure what that does, if anything.
The documentation doesn't really explain "how" multiple users are supposed to behave within a composite project. If Eviware could elaborate on that, I think it would be most helpful in troubleshooting these inconsistencies. We, as users, may very well be doing something the product is allowing us to do but is not intended.
Also, I'm curious as to why there is not a "Save Suite" Composite Action? Having to save all of the test cases in a suite can get a bit time-consuming.
Thanks.
Related Content
- 7 years agoJSoul