I just started using Jmeter a couple of weeks ago.
This week the JMeter 1.7 final was released. Thanks for all the effort of the
developers.
Now I'm wondering what phase the development enters ?
- a brainstorming for all wanted new features ? (I see there is a TODO on the web page)
- or is it full steam ahead on development on features which has already been decided
on ?
Assuming that a little brainstorming can be useful :
Here are some of my "wishes", briefly described.
1.
add a JNLP file for JMeter, and put in on the JMeter web page
This will allow people who has JavaWebStart to launch the JMeter app of internet,
without
having to install it on their machines.
This will also be kind of "PR" for the product, as it will be very easy to start it,
and test it,
and then probably download the distribution if you want to use it more.
I can make the JNLP file, but someone need to have a certificate to use for signing the
jar files, and also have access to set it up on the web site.
2.
make it possible for different parts of JMeter to know when a test run starts and
stops.
I think this is already on the TODO list
3.
As mentioned by me earlier in a emai, I plan to use JMeter for testing our application
server
(a properitary app server).
It seems like JMeter is mostly used for testing web pages, ftp and JDBC.
Are people interrested in using it for testing of other stuff ?
Are people currently using JMeter to test "strange things" ?
One thing which I think I need because of this, is a general "ConnectionManager"
interface,
which can have config elements, and which can be access by the test samplers.
This interface can also be used by the JDBC test smaplers, and possible the FTP
samplers.
I want to be able to set up the following test plan
Thread group
MyAppServerConnectionManager
SimpleController
ExecuteTask (a test sample controller)
ExecuteTask (a test sample controller)
ExecuteTask (a test sample controller)
For each thread running, the MyAppServerConnectionManager will make a connection to
my app server.
Then each ExecuteTask will execute a task on my app server, asking the
MyAppServerConnectionManager for the connection to use.
When the test run stops, or the user exits the JMeter, the
MyAppServerConnectionManager
received an event, so that it can close all existing connections.
I think this will be useful also in the JDBC test plan.
Thread group
JDBCConnectionManager
SimpleController
JDBC request
JDBC request
JDBC request
Here the JDBCConnectionManager can be responsible for having a connection pool as well.
Perhaps also in the FTP case (if you want to test just file download speed, not
include the opening / closing of the FTP conncetion)
Thread group
FTPConnectionManager
SimpleController
FTP request
FTP request
FTP request
Regards
Alf Hogemark
