Today when your function requires some context or access to JMeterVariables , the test will fails. There is room for improvement: - Have a JMeterVariables in JMeterContext - Propose 2 text areas (setup/teardown) where some groovy code could be added to setup the context / variables with mock data The FHD would run the groovy code before the execute and after it.
Implemented in a bit different way: - We show a new zone to display JMeterVariables that stays available between function calls - User can reset it on demand - User can use any function to set additional variables or properties using __groovy or __BeanShell
Author: pmouawad Date: Sat Sep 8 16:27:24 2018 New Revision: 1840368 URL: http://svn.apache.org/viewvc?rev=1840368&view=rev Log: Bug 61834 - Function Helper Dialog : Improve tests by showing variables and keeping them available between evaluations Bugzilla Id: 61834 Modified: jmeter/trunk/src/core/org/apache/jmeter/functions/gui/FunctionHelper.java jmeter/trunk/src/core/org/apache/jmeter/resources/messages.properties jmeter/trunk/src/core/org/apache/jmeter/resources/messages_fr.properties jmeter/trunk/xdocs/changes.xml
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4624