@sebb : That was just a bit of pseudo-code to get the idea across. As you also correctly indicated your comment in the feature request in BugZilla: yes instead of a TestResult class it would more effectively be a call-back interface. All very much true, my point is to put it on the agenda of the developers, not to tell them how to implement it.
With regards to your suggestion to provide a patch: I do not have any experience with JMeter internals. I do not think that such a refactor is something for a patch, most definitely not by a noob like me. The way I see it; it is about separation between the GUI part of JMeter and the engine/core/driver. From my point of view it might even be two distinct components with a well defined API in between. The GUI would then depend on the engine part and the engine part would be usable without the GUI. At least, that is how it looks in my dreams. I would really much like to hear from the JMeter developers how they think about this: Is it feasible? Does it require a lot of work? Is something they might want to pick up anytime? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
