This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
Prelude I have just finished preparing the first version of a web-based multi-threaded testing tool using servlets, jsp, xml. The simplified view of the work strategy is as follows - it works currently as stand-alone, uses URLConnection to hit a web page, divides the number of hits in as many threads, saves the response as XML file and later when testers run test script for that web page, compares the actual response with the saved response. Current Scenario Now I have started thinking on the second version that must handle distributed loads. That means earlier while I was using one tomcat server, now I've to use many servers in a network, distribute the threads using some pre-defined conventions so that each web server starts hitting the same and different web pages at a time and then the distributed responses will be accumulated and forwarded to the central server where the response results will be finally saved. Moreover I have to find out way how dependent test scripts will execute where one test script must wait until the earlier test script's response is received. Technologies I am thinking to use web services, particularly Apache Axis for distributed test script execution. So the MVC pattern I weas using is led by a front controller servlet and now I would like to add a parallal servlet that works as a client to distributed services. Comments & Sugessions I would highly appreciate your comments and sugessions regarding the scenario, the technologies and alternate proposals from you. Regards,
Ashik Uzzaman Senior Member of Technical Staff, Salesforce.com, San Francisco, CA, USA.
subject: Designing load distribution and test dependency