As does rival Proxy Sniffer, PureLoad supports single-machine as well as distributed load testing using Unix-, Linux-, and
Windows-based load clients. For this review, I focused on how well PureLoad's Web technology testing facilities compared with
that of rivals OpenSTA and Proxy Sniffer.
After starting PureLoad's services as outlined in the documentation, the next step is to launch the product's console. Defining
a load test is very easy with PureLoad. After defining workers (virtual users), I then went on to create a series of scenarios
(scripts).
PureLoad offers three very strong options for script creation. Test developers can choose to manually add tasks, such as an
HTTP post task, to a scenario from the 70 built-in functions, or they can create custom tasks.
The second method of script creation would be to use PureLoad's Web Crawler tool, which crawls a Web site or application for
static content and structure. This information can then be saved or copied into a scenario and be used as a foundation for
a load test. The third method of script creation is provided by an included HTTP recorder, which captures interactive browser-session
activity as the basis for a load test.
I found that each approach was solid and the different methods were complementary to one another. For example, after recording
and executing a script, I was able to identify one area of my test Web site that was performing slower than expected under
load. Using manual script creation, I was then able to focus a second round of testing on just that portion of the site.
Likewise, after defining the test site URL and the depth to scan in the Web Crawler utility, PureLoad accurately captured
the content and structure of my site. I was then able to add some tasks manually to provide variable input during a load test
from a file.
During the tests, PureLoad provided data and charts as it recorded the results of the execution. I was able to view overall
metrics, such as successful and failed tasks and response time data, or drill down to the individual virtual user level to
view the same types of metrics. At the conclusion of the test, the same metrics were then available for review and exporting.
Overall, PureLoad's reporting metrics are not as detailed as those found in Proxy Sniffer, but most testers should find them
more than adequate.
PureLoad includes a load-test comparison tool, and after comparing the output of several load test runs, I found it to be
on par with the comparison functionality provided by Proxy Sniffer. I also found it useful to export test data from PureLoad
to a series of spreadsheets (CSV) and chart images (PNG) to perform further trend analysis.
Sites considering adoption of load-testing tools should evaluate PureLoad. In particular, its strong scripting facilities
and added capability to support performance testing of both Web and enterprise apps make it appealing.
Any of the three tools tested here would be a useful addition to the toolboxes of enterprise performance-testing teams. OpenSTA
provides solid core of Web load-testing tools at a budget-minded price, whereas PureLoad is an ideal fit for load testing
Web and other enterprise technologies. Teams that need a full-featured Web load-testing tool at a reasonable price should
definitely give Proxy Sniffer a test drive.