Your browser does not support JavaScript!
http://iet.metastore.ingenta.com
1887

Performance Testing - A Case Study of a Combined Web/Telephony System

Performance Testing - A Case Study of a Combined Web/Telephony System

For access to this article, please select a purchase option:

Buy chapter PDF
£10.00
(plus tax if applicable)
Buy Knowledge Pack
10 chapters for £75.00
(plus taxes if applicable)

IET members benefit from discounts to all IET publications and free access to E&T Magazine. If you are an IET member, log in to your account and the discounts will automatically be applied.

Learn more about IET membership 

Recommend Title Publication to library

You must fill out fields marked with: *

Librarian details
Name:*
Email:*
Your details
Name:*
Email:*
Department:*
Why are you recommending this title?
Select reason:
 
 
 
 
 
Telecommunications Performance Engineering — Recommend this title to your library

Thank you

Your recommendation has been sent to your librarian.

In its most abstract sense performance testing is the loading of a system, or a part of a system, with a synthetic workload, i.e. taking a real system and using specialist scripts and tools to emulate the activities of multiple users (where a user may be another system) performing typical user actions. Atypical workloads are sometimes used to stretch a system to, and beyond, the anticipated limit to add confidence that it will be able to support.What differentiates performance testing is that the focus of the work is on a real system with a controlled load rather than a chapter or computer simulation-based exercise, or a live system with a live and uncontrolled load. An advantage that performance testing has is that it works with the full complexity of the system in its implemented state, rather than a simplified model, or how it should work according to the design. The downside is that testing can only begin when there is something to test and this is inevitably later in the life cycle than other forms of performanceengineering, and obviously major problems found at a late stage are more costly to fix than if they had been found at an earlier point in time.However, as many modern systems are an integration of specialist components bought in from third parties, who may be reluctant to share details of how their product operates for good commercial reasons, performance testing may be the first opportunity for the integrator to find out if the components being used to build the system live up to their specifications and expectations. It should be noted that performance testing is not limited to a particular technology, although the choice of tools used may be strongly linked to either the underlying technology or to the system interfaces where work is presented.

Inspec keywords: user interfaces; telecommunication computing; software performance evaluation; Internet telephony; program testing

Other keywords: system loading; specialist scripts; performance engineering; controlled load; specialist components; combined Web/telephony system; performance testing; synthetic workload; full system complexity; life cycle; system interfaces

Subjects: Telephony

Preview this chapter:
Zoom in
Zoomout

Performance Testing - A Case Study of a Combined Web/Telephony System, Page 1 of 2

| /docserver/preview/fulltext/books/te/pbbt007e/PBBT007E_ch6-1.gif /docserver/preview/fulltext/books/te/pbbt007e/PBBT007E_ch6-2.gif

Related content

content/books/10.1049/pbbt007e_ch6
pub_keyword,iet_inspecKeyword,pub_concept
6
6
Loading
This is a required field
Please enter a valid email address