-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Search Feature : Enhance it with ability to replace #3052
Comments
@pmouawad (migrated from Bugzilla): Current patch has one bug for now that I didn't resolve yet (ideas welcome). Created attachment BUG_54525.patch: Patch implementing the replace for Samplers |
@pmouawad (migrated from Bugzilla): URL: http://svn.apache.org/viewvc?rev=1775729&view=rev Added: |
@pmouawad (migrated from Bugzilla): URL: http://svn.apache.org/viewvc?rev=1781476&view=rev Added: |
@pmouawad (migrated from Bugzilla): URL: http://svn.apache.org/viewvc?rev=1781992&view=rev Modified: |
@pmouawad (migrated from Bugzilla): URL: http://svn.apache.org/viewvc?rev=1784115&view=rev Modified: |
oliver lloyd (Bug 54525):
The ability to search and replace when creating new variables would be very useful.
Essentially what I do at the moment is create the variable, close the testplan and then use sed to find some string, say 'mysername.com', and replace it with '${server}'. This process works but it's slow and it would be a substantial enhancement if this were possible in the GUI - maybe via the Seach menu. It would be an even greater enhancement if there were a button available on the User Defined Variables form that would allow me to directly:
"Find any occurrences of the [MYVALUE] string and replace with '${[MYVARNAME]}'".
The added benefit here is saving the time, risk and effort of having to go through the plan and complete this process manually.
It's worth noting that in pretty much every single case where a var is created then this find and replace action is required, so it may as well be made easier.
Relates to #1185.
OS: All
The text was updated successfully, but these errors were encountered: