> From: Ilia Iourovitski [mailto:[EMAIL PROTECTED]] > > Isn't it better to embed Jython into JMeter like MAXQ > does. > http://www.bitmechanic.com/projects/maxq/ > It will let users write real scripts. After all JMeter > about measurements. All tools like Silk Performer has > it. And it is much easier to debug jython script than > long set of tests.
I have to agree with Ilia. It would be a much better use of your time to use an already developed scripting language and merely provide hooks to bind to JMeter. One big point that we need to make here is that as soon as we start working with scripts, JMeter becomes more a functional testing tool than a load testing tool. There is a lot of need for functional testing. Another point to tack on to that is that we can test how the server degrades with more clients, but we can't trust the numbers as actual hard numbers. We can only determine trends. That said, I think the best way to find the balance is to #1) provide the scripting language bindings, and #2) fine tune the reporting to reflect trends. For instance, it would be really helpful to find the saturation curve for a webapp. The scripting language can probably even be used to cull the results and determine the ratio of bad responses to good responses or other intelligent data mining. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
