Archives

The Grinder is a load testing framework that makes it easy to run a distributed test using many load injector machines. Test scripts are written in Jython, and can call out to arbitrary Java code, providing support for testing a large range of network protocols.changelog V-3 :

The TCPSniffer has been renamed TCPProxy for correctness. The TCPProxy can be used with other HTTP and HTTPS proxies. Many new features and fixes have been added to the TCPProxy.

Console signals are now transmitted over a TCP socket connection. Multicast is no longer used, removing a frequent source of setup problems.

The interface that plug-ins must implement has changed significantly. Plug-ins written for The Grinder 2 will not work with The Grinder 3.

Many grinder.properties have been removed. The features formerly accessed through setting properties are now set by making calls to the plug-in from test scripts. Some of the remaining property names have been renamed.

HTTP tests can now be directed through an HTTP proxy.

String beans and OK strings have been removed from the HTTP plug-in. String beans and OK strings are very limited in comparison to to the flexibility now provided by Jython scripts.

The HttpURLConnection implementation has been removed from the HTTP plug-in.

Many other minor updates to HTTP testing functionality.

HTTPS and SSL contexts can now be controlled on a per thread basis.

The JUnit and Socket plug-ins have been removed. Their functionality can be achieved directly by using the appropriate Java objects in scripts.

From the console you can edit test scripts and distribute them to the worker processes. It is no longer be necessary to copy grinder.properties files around or to use a shared disk.