I've released the first official version of the loadtest module on drupal.org. Most of the documentation on using the module is contained in the README.txt. The module seems to be working pretty well at this point, with the biggest issue being the apache timeout setting killing the tests while their running. So if you try it out, be sure to set apache's timeout to a large enough value that all of the tests can run without being killed.
Since my last post I've added a few new features to the module including:
* interface for deleting all records in the database
* interface to export all records to a CVS file
* ajax progress indicator
* user configurable options for tests
There are still a few things I'd like to add to the module that I never got a chance to during the Summer of Code. The state interface allows users to save the state of their site, but only saves the modules. The user needs to manually run any variable_set that they want to record. I think I'd like to replace this feature with perhaps another module that allows users to change install profiles on the site. In this sense the state will be an install profile, and will have all of the power that an install profile has.
Thanks to all my mentors... Khalid Baheyeldin, Rok Zlender, and Owen Barton for all your help with this project and your good ideas :). And to everyone else who helped me out with various aspects of the project and issues I had, including the Bryght guys for letting me work out of your office space and bug you with questions when I had them.
I plan on carrying on with this project after SoC so hopefully I'll still see all you other SoC-ers around :).
Comments
In case it helps
cvs.module has some lines of code that go like this:
<?php// Set timeout limit to 3600 seconds as it can take a long time to process the log initially.
if (!ini_get("safe_mode")) {
set_time_limit(3600);
}
?>
Don't know if that fits into your module or situation, but it might be appropriate.