From the Grinder tool website:

"The Grinder is a Java load testing framework that makes it easy to run a distributed test using many load injector machines. [...] Load test anything that has a Java API. This includes common cases such as HTTP web servers, SOAP and REST web services, and application servers (CORBA, RMI, JMS, EJBs), as well as custom protocols. [...] Tests are written in the powerful Jython scripting language. [...] A graphical console allows multiple load injectors to be monitored and controlled, and provides centralised script editing and distribution. [...] Automatic management of client connections and cookies. SSL. Proxy aware. Connection throttling. Sophisticated record and replay of the interaction between a browser and a web site."

Found an interesting post on a tool for testing small screen rendering in FireFox. The tool is Small Screen Rendering XPI by Disruptive Innovations. It's an extension to the Mozilla Application Suite which allows you to check if a web site renders well on mobile devices.

Many times, when testing websites, we forget about the static content of the site. Here is a simple tool that applies some simple heuristics to help gauge the effectiveness of the content on your site. Even if you don't end up using it, as you read through it you can get some ideas for how to make content more accessible.

benerator supports load and performance testing by providing a framework for generating high-volume test data. From the tool's website, out of the box benerator supports database systems, XML, XML Schema, CSV, Flat Files and Excel. Domain packages provide reusable generators for creating domain-specific data as names and addresses internationalizable in language and region (via nestable datasets).



A commercial version is available in addition to the free GPL version.

Today's tip comes from Chris Wallace. In his post on The last browser testing advice you'll ever need he talks about his coding and testing process, lays out the a-grade list of browsers (from the Yahoo! UI Library), and if you take the time to read the comments you'll see several tips from readers of the site (including this link to the multiple IE installer).

Worth the time, read it if you can.