Your e-Business Quality Partner eValid™ -- Automated Web Quality Solution
Browser-Based, Client-Side, Functional Testing & Validation,
Load & Performance Tuning, Page Timing, Website Analysis,
and Rich Internet Application Monitoring.
© Copyright 2000-2010 by Software Research, Inc.

eValid PerformanceTest™ — Service Parameters
Overview
Details
Parameters
Loading Schedule
Summary
Service Request

eValid's Fixed-Price PerformanceTest projects allow firms to increase their ROI on limited testing budgets -- without the need to invest in tools, people and training. You get top-notch state-of-the-art validation of server capacity to help assure end-user satisfaction.

Typical Project Parameters.
The table below gives typical parameters for three levels of the Performance Testing Program. These estimates may vary depending on the details of the web application or WebSite being tested.

PerformanceTest Project Parameters
Package Name > BRONZE SILVER GOLD PLATINUM DIAMOND
Project Effort Days2 3 4 5 6
Project Elapsed Days4 6 8 10 12
Scripts Produced2 3 4 56
Total Script Playback Time Recorded Yes Yes Yes YesYes
Scenarios Produced 1 2 3 45
Number of Interview Calls 23456
Scripting Effort-Hours 23456
Browser Emulated Users (EUs) 500 1,000 2,000 3,000 5,000
HTTP Virtual Users (VUs) 4,500 9,000 18,000 27,000 45,000
Total Users (EUs + VUs) Emulated 5,00010,00020,00030,00050,000
Maximum Number of Machines 5 10 [*C*] 20 [*C*] 30 [*C*] 40 [*C*]
Maximum Bandwidth (Download Mbps) 3.4 [*C*] [*C*] [*C*][*C*]
Ramp Step Size, EUs 63 125 250 375 500
Ramp Step Size, VUs 563 844 1,1251,625 2,000
Total EU Run Hours 250 375 500 1,000 2,000
Total Delivered Browser-Hours 2,750 5,000 10,000 15,000 25,000

Notes

  1. There is a specified upper bound on script development time. Script development assumes a well-behaved, non-changing web application that does not contain internal JavaScript errors.
  2. Specification of parametric data for scripts using DataSynthesis or eV.Generate operation is available but is not included.
  3. The VU scripts used are those that arise from automatic creation of the URL.trace.evs file from one or more of the functional tests.
  4. Each functional test will be supplied to customer for one cycle of confirmation and cannot be changed after that confirmation is received.
  5. The total number of actual user run hours for all machines and machine images used includes all of the repetitions in the run. For a typical 3-minute average EU playback time, each hour of operation for one "track" in the scenario implies 20 repeats of that script. In the smallest scenario, with these assumptions, the total script repetitions is 500 * 20 = 60,000
  6. A stable Application Under Test (AUT) is assumed; changes in the AUT that invalidate scripts will require e project restart.

Effective 15 October 2009. Prices and delivery terms subject to change without notice. The standard eValid Software License applies.