THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
*Navigation trail:* \["JMeterProjectPages"\] - \["JMeterDevelopment"\] - \["JMeterDevelopment"\]/LongTerm Wiki Markup
...
<strong>JMeter GUI Classes and TestElements</strong>
...
- Regarding probs 1,2: forget about allowing multiple GUI's serve the same TestElement. It's a minor inconvenience to have to create new empty classes for each new GUI.
- If a tool was written that searched through JMeter's jars and compiled an XML document that specified all the necessary information, it would greatly reduce the work a developer would have to do.unmigrated-wiki-markup
- Does the mapping have to be reversible? Surely all an external test developer needs is to provide a valid GUI for a given test element? In which case, all that needs to be done is to provide a _preferred_ GUI class for each test element.\["sebb"\]