Overview

Today more than ever performance testing is an integral step in satisfying customers demand on your applications, systems and components. They expect quick execution of any request or action. They want constant usability. For large systems, they expect that they will not be affected by what someone else is doing. How do you ensure your product meets these exacting performance standards ? Using eggPlant for Performance Testing, you can!
Application Performance Testing is conducted to determine if an application, system or component meets such metrics as responding in an appropriate amount of time or handling an acceptable number of connections. Stress or Load tests are one type of Performance Testing that can often be automated with a test tool that simulates multiple users. Common deficiencies encountered during this phase of performance testing are related to things like slow execution cycles, data corruption, or complete system failure.

There are a number of different methods one can use to create a performance test with eggPlant. eggPlant application performance testing tool can time individual events or sequences of events, and it can be used either to generate small loads or to enhance an existing load test scenario by simulating real user interactions while another tool creates an artificial load on the application.

Below is an example of how proven tools for testing, such as eggPlant dramatically simplify  performance testing.

Performance Testing Example

GIMP is the GNU Image Manipulation Program. It is freely distributed and used for such tasks as photo retouching, image composition, and image authoring.

Test Objectives:
To determine the performance impact of having multiple images open for GIMP.
To determine the number of open images that the system can handle — the threshold that the system will allow.

Test Specs:

  • Operating System: Linux RedHat 7.1
  • Kernel: 2.4.2
  • Desktop: Gnome
  • Application: GIMP 1.2.1

Test Details
Our test example will use one 678×435 jpeg image with a file size of 35754 bytes. The sample image must reside in the home directory of the current user and will be named eggplant.jpg. For consistency, no other UI applications will be allowed to run concurrently with GIMP.

The following settings for GIMP will be used:

  • Tip of the day will be disabled.
  • All other windows, with the exception of GIMP’s main window, will be hidden from view.

Test execution will consist of the following:

  1. Launch GIMP from the Gnome menu bar.
  2. Open a new image using the Control-o keyboard shortcut.
  3. Wait for the “Load Image” window to appear.
  4. Wait for the “Load Image” window to appear.
  5. Proceed by selecting “eggplant.jpg”..
  6. Press Enter to open the image.
  7. Measure the amount of time that it takes for GIMP to load the image. The time limit for an image to open will be set to 10 seconds. Once the threshold is reached end the test.
  8. Log the time.
  9. Repeat steps 2 through 8.

Scripts: Click script: The execution will commence from this script

* The GIMP is used here only as convenient, readily available example application. Its use here should not be construed as an endorsement of eggPlant by the GIMP developers nor as suggesting that the GIMP team is a customer of TestPlant Inc.

Download – eggPlant load testing data sheet

Comments are closed.