suisuilian

 Web性能测试基本性能指标来源：考试大   【考试大：我的学习乐园,我的考试专家】   2009年4月7日　　WEB性能测试的部分概念一般来说，一个web请求的处理包括以下步骤：
　　（1）客户发送请求；
　　（2）web server接受到请求，进行处理；
　　（3）web server向DB获取数据；
　　（4）web server生成用户请求的object（页面），返回给用户。从客户发送请求开始到客户接收到最后一个字节的时间成为响应时间（第三步不包括在每次请求处理中）。
　　1.事务（Transaction）
　　在web性能测试中，一个事务表示一个“从用户－>web Server－>DB－>web server－>用户”的过程，一般的响应时间都是针对事务而言的。
　　2.响应时间
　　响应时间指的是从客户端发起一个请求开始，到客户端接收到从服务器端返回的响应结束，这个过程所耗费的时间。在某些工具中，响应时间通常会称为 “TTLB”，即“time to last byte”，意思是从发起一个请求开始，到客户端收到最后一个字节的响应所耗费的时间。响应时间的单位一般为“秒”或者“毫秒”。一个公式可以表示：响应时间= 网络响应时间 + 应用程序响应时间
　　3.并发数
　　并发数是指同时进行请求的客户的数量，并发数用于模拟用户的真实负载情况（并发情况是对系统最大的考验），并发数≠同时使用系统的用户数。
　　4.吞吐量
　　吞吐量指的是单位时间内处理的客户端请求数量。通常情况下，吞吐量用请求数/秒或者页面数/秒来衡量。从业务角度看，吞吐量也可以用访问人数/天 或者页面访问量/天 来衡量。
　　5.资源利用率
　　资源利用率指的是对不同系统资源的使用程度，例如服务器的CPU（s），内存，网络带宽等。资源利用率通常以占用最大值的百分比 n %来衡量。

 

核心业务场景测试
组合业务场景测试
大数据量测试
强度测试

response times, transaction rates,

 

Following are the only few attributes out many that considered during performance testing
CPU usage
Memory usage {Memory leakages, thread leakage}
All queues and IO waits
Bottlenecks {Memory, cache, process, processor, disk and network}
Network Usage {Bytes, packets, segments, frames received and sent per sec, Bytes
Total/sec, Current Bandwidth Connection Failures, Connections Active, failures at
network interface lever and protocol level}
Database Problem {Settings and configuration, Usage, Read/sec, Write/sec, any
locking, queries, compilation error}
Web server {request and response per seconds, services succeeded and failed, server
problem if any}
Response Time
Throughput
Screen transition
Time {Session time, reboot time, printing time, transaction time, task execution time}
Hits per second, Request per seconds, Transaction per seconds
Performance measurement with number of users.
Performance measurement with other interacting application or task

 

 

Requirement Study
• Project Initiation
• Analyzing Test Goals and Objective
• Determining test scope
• Analyzing HW and SW
requirements.
• Test Initiation Checklist

Test Plan, Test strategies.
• Selection of testing tools.
Generating Test Scenarios
/Scripts.
• Reviewing the test documents
and Base lining.
• Test Readiness Review

• Performance Test Scenario / Script
Execution.
• Collect the Data.
• Analyze the Data.
• Problem Investigation like bottlenecks
(memory, disk, processor, process,
cache, network, etc.) resource usage
like (memory, CPU, network, etc.,)
• Generate the Performance analysis
reports containing all performance
attributes of the application.
• Create Recommendation report based
on the analysis.
• Repeat the above test for the new
build received from client after fixing
the bugs and implementing the
recommendations

Set up the environment as per
the requirement
• Installation of OS and software
and testing tools
• Test readiness review.

• Performance
• Test Report Generation
• Updating test documents
• Post implementation review
• Project completion checklist

 

　　1.事务（Transaction）

　　2.响应时间
Response Time
　　3.并发数
Concurrent number
　　4.吞吐量
Throughput
　　5.资源利用率
CPU usage
Memory usage {Memory leakages, thread leakage}

Bottlenecks {Memory, cache, process, processor, disk and network}

Check the Transaction, Response Time

acceptable response time

 

34

Performance Test Scope:
Scenarios test for core business transactions
Scenarios test for combination business transactions
For Example,
Download Maximum files from server;

Volumn Test
Volume testing subjects the target-of-test to large amounts of data to determine if limits are reached that cause the software to fail. Volume testing also identifies the continuous maximum load or volume the target-of-test can handle for a given period.

For Example, Some users have large amouts of solutions in DB.

Stress Test

Success criteria:
Meet performance Requirements:

Performance test case preparation:
TestEnvironment Preparation:
Training