Load Testing

Hi!
Could somebody please suggest how to perform load testing using EggPlant?
At first - common thoughts

Or give the link where i can read about this...

Thanks!

Comments

  • ToddTodd Member
    edited June 2007
    Since load testing is really a nebulous term used by many practices with various meanings, we may want to standardize on what you are considering load testing and the criteria in which that testing will be carried out.

    http://en.wikipedia.org/wiki/Load_testing

    If you would specify what it is you are interested in testing, specifically the software in mind I may be able to help in a more than general way.

    The general concept of load testing can be carried out by Eggplant scripts by designing a test suite against a system to be tested (the system under test) using Eggplant, when run in multiple occurences (possibly with the CLI runscript option and many license key available to our customers as a contract option) can 'slam' or load test a system and validate that a given service/system will perform within specifications/tolerances.

    Without disclosing names, we have many clients that are quite happy using hundreds of instances of Eggplant running concurrently to test web apps, in house closed apps (not public via the web) as well as hardware and other devices that are in need of multiple requests for information at a given time.

    So, load testing as it is specified by the need to document and respond to a services ability to provide a defined service is something that Eggplant address at some large installation (and small :).
  • then get eggplant to do it faster and longer. I've done some web system testing by writing a script that would run on three machines, then execute the script on system one, and once it was uplaoding a thousand records, switch to system two and do the same thing, then on to system three, back to system one just as the upload was finishing and do it all again. With multiple command line license it's a bit simpler, but for a single licnese, design a test that can be started and finsihed without direct actions and then execeute it on some other machines.

    For single machine testing, it's a whole lot simpler, data driven loops or if your an ambitious sort, a random number generator feeding a looping script.

    We've recently used ep to test an web system that tracks image revision with a simple looping script we ran three hundred images thru the system and checked to assure each image targeted was actually displayed.

    load testing is a great application for ep, as it works well past the time that the cleaining crew has left your offices

    Think human first, then "eggplantit"

    (eggplantit is a cute saying originated by Mr.P) :idea:
  • oldyewoldyew Member
    Thank you for your response!

    I try to describe which type of testing is needed.

    We have client-server application. It's online game application.
    Client side is implemented with delphi and flash.
    we need to check how the application will work with load in 2000 users.

    Could you please suggest how can we check this using EggPlant?
  • ToddTodd Member
    edited June 2007
    You would need to simply design a test that would run a game sequence (or maybe a few tests that would run various game sequences) and then run 2000+ instances of Eggplant CLI against your game servers. Its a perfect match for Eggplant IMHO. If you would like us to call you and talk (yep, I work for Redstone Softwawre) about a Proof of Concept for your situation, please let us know. You can contact Redstone Sales Group [email protected] and talk to Emma Campbell, Global Sales Manager.
  • oldyewoldyew Member
    Thanks for your advice.
    I'll try to find mentioned functionality and play with it.
    And after that:) i'll connect with you if i have any problems.
Sign In or Register to comment.