> 3/ Long-term development plan > > At the very least, we need to agree on a > loose high-level end-user requirement list [I think I already have a > document of this kind somewhere -- the one I used to select JMeter > among other tools quite a few months ago].
I'm guessing this might be drastic, but I feel like my hands are tied while using the GUI to put together a test plan. Maybe it's the developer in me, but has anyone considered the ability to put together a test plan that's described in, say, ECMAScript, with scriptable objects we create? Then, the GUI is only a helper to generate the ECMAScript. At a later point, you could tweak everything with a "view source" of sorts. On the other points being made lately, my contribution rate is definitely cyclical based on when I'm required to use Jmeter. Another usage time is coming up within a couple months - at which point I'll turn into an active contributor again. My company just won't pay me to work on projects I'm not using - no matter how hard I've tried to see if I could push that through. ;-) +1 on the [VOTE]. -1 on the [DISCUSSION] (that's implied) Jim -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
