PureLoad

Key Features

PureLoad is a load testing tool that allows testing of server applications using a distributed runtime environment.

A load test session using PureLoad to test a web application typically involves the following steps:

1. Set up the HTTP Recorder and navigate the site you want to test using a standard browser. Scenarios will be created automatically.
2. Test, debug and verify you recorded scenario using the graphical GUI.
3. Optionally define server monitoring to be used
4. Launch your test, and analyze in real-time response times, transactions per second, server monitor data etc.
5. Export and analyze results.

Platform Independent: PureLoad is implemented in Java and runs on all platforms supporting Java 1.5 or higher. We verify PureLoad on Windows, Mac OS X, Linux and Solaris.

Distributed: PureLoad uses a distributed architecture, where load can be generated from a single machine or distributed on multiple machines. The distributed architecture of the product allows load generation, simulating thousands of virtual users, using a combination of several Windows and/or Unix hosts. The distributed architecture in combination with the platform independence means that you may use any (or most) hardware resources you have available.

Testing Web Apps: PureLoad includes extensive support for testing web applications using HTTP/HTTPS.

- HTTP Methods
- Headers and Cookies
- HTTPS/SSL
- Dynamic Web Applications
- HTTP Recorder
- Web Crawler

Web Technologies: PureLoad is targeted at web applications that use standard server technologies such as:

- JavaEE
- ASP
- .NET/C#
- PHP
- Ruby

Supporting web servers such as:

- Apache and Tomcat
- IIS
- Weblogic

Console GUI: From the intuitive graphical user interface of the console application all actions required to set up the environment, define scenarios and control the load execution is performed. The Console is the single point of control in a PureLoad runtime environment.

Results: In the Console applications results are displayed during and after execution of a test.

- Metrics
- Real-time Graphs
- Reports
- Result Comparer

Benefits

Why Use PureLoad?

• Ease Of Use – “Load testing made easy” – No scripting language or programming required, everything controlled from GUI
• Securing your business – Expect success with you server applications, be prepared!
• Scalable and high performance - Scale from low end web testing to high end telecom services
• Extensive support for testing web applications and more - Test web applications created using JavaEE, .NET, PHP, AJAX, SOAP, ASP, CGI etc. Use Enterprise Edition to test other server applications.
• Cost effective - Affordable Prices, platform independent allows you to use available hardware and no advanced training required.

New Releases

PureLoad 4.1.3 – Change Log
2010-11-30
Minor Enhancements

• Distribution: New “ramp-up” linear distribution
• Console: Display Thread Usage i Worker Pane
• Console: Add date as well as time in time slot result information (table)
• Sequence/Task iterations: Number of iterations doesn’t support variables
• Console: Add workers dialog now allows specifying logical name and thread settings

Bugs fixed

• Console: HttpPostFileTask might freeze console when running in debug mode
• Console: Removing worker threads (Edit->Remove Threads…) is slow
• Conditional sequences: Execute always makes sub-sequences to execute, even if conditions specified
• Http Tasks: Counting bytes might cause errors
• HTTP Tasks: Timing bug in BandwidthLimitInputStream (“timeout value is negative”)
• HttpInitTask: proxy information not cleared
• Worker: ConcurrentModificationException in worker log
• Worker/Manager: Memory usage high (even if not reporting results per thread)
• Worker: RMI timeouts when workers running with high load
• Workers: No response (“dead”) when running out o memory. Not possible to get worker log or failed tasks.
• IP Pool Tasks: Extra thread created when executing
• TimeTask, EchoTask and FTP tasks: Can’t set local IP address or remote port
• SleepTask: not reporting correct times in multi treading mode
• Workers: memory monitoring improvements
• Conditional Sequences: performance and memory usage improvements

---

PureLoad 4.1.1 – Change Log
2010-06-04
Bugs Fixed and Minor Enhancements

• Console: Copy/Paste scenario sometimes takes very long time (heap memory complaints)
• HTTP Recorder: clear UI state in recorder window if failed to start proxy server
• Console: ask if PLC file to be saved before disconnecting
• Console: Log and Debug views includes only ‘time’ not ‘date’ for each entry
• Console: When adding worker threads the window focus should change to the “pop-up” window.
• HTTP Recorder: add option to disable default naming of task as “image” and/or “application”
• Console: Not possible to remove worker threads (if thread information not reported)
• Console: Generate report; new directory not automatically created
• Console: if quitting and save to file is cancelled, console still exits
• GetHTMLPageTask: local host settings (via HttpInitTask) doesn’t work if more than one thread used
• Failed tasks view: not clear in GUI when/how failed tasks is updated
• Workers: Messages written to stdout is logged as [Error] in worker log
• Console: add operation to clear worker log

Download

Click here to download the evaluation of PureLoad

Prices

For further pricing information, contact info@codework-solutions.com.