Auto update references to variable when variable name is changed
Right now, when you rename a variable from name "x" to "y", the (keyword)tests in which these variables are used are not updated. When run they fail with an exception. In my opinion the link should be maintained (ie. when the name is updated the code in which the variable name is used should be updated as well). Similar like now already implemented in name mapping (renaming aliases results in updating the keyword scripts, very handy!).
How to update huge test cases using csv import.
Hello 🙂 We are using Zephyr Scale (server) 10000 users. Many testers want to update test cases using excel/csv updates. Currently, however, Zephyr scale seems to only support importing new test cases. Is there any way or plan that I can import to update the already registered test case? ThanksUpdate Custom Property references in "Run Test Case" values, if Custom Property is renamed
It would be great, if ReadyAPI/SoapUI NG would update usages of custom properties in case of renaming the custom property, even if there are used in the value part of the property definiton of "Run Test Case" test steps. 1. Create TestSuite Repro - Custom Property MyRepro 2. Create TestCase Foo - Custom Property MyFoo 3. Create TestCase Bar 3a. Create TestStep "Run TestCase Foo" in TestCase "Bar" 3b. Assign to "MyFoo" the value value ${#TestSuite#MyRepro} 4. Rename the Custom Property "MyRepro" to "MyNewRepro" 5. Check the value in TestStep "Run TestCase Foo" -> Value is still "${#TestSuite#MyRepro}" and not "${#TestSuite#MyNewRepro}" If the custom property is used in a "Soap Request" test step, the usage is updated. So it would be a great help, if same happens in case of usages in "Run TestCase" test steps. With regards
Add Option to Update TestExecute node machines automatically
It would be nice if there were an option/setting with TestExecute to choose to always go ahead and download & install the latest updates automatically. This would be ideal for lab situations where there are multiple machines that need to get the update. If users had a lab that they wanted to control more manually, then they could simply uncheck this option. *We are aware of the silent install option and will be using that in the meantime, but this will first require us to be aware of an update and download the installation package first before updating the lab machines.
