Sie sind auf Seite 1von 28

Quality Control L&P Testing - Overview

AGENDA
Introduction Definition / Purpose / Pre-Requisites Factors governing L&P testing Methodology for L&P testing
Collecting requirements for L&P testing Writing test cases for L&P testing Automating L&P test cases Executing L&P test cases Analyzing L&P test results Tools for L&P testing

Process for L&P testing Exercises, Q&A, Summary

L&P Testing - Definition


To evaluate the response time, throughput and utilization of the system, to perform its required functions in comparison with the different versions of same products(s) or with different competitive product(s)

Purpose of L&P Testing


To measure the effects on application behavior with the defined user load. To measure the average page response time and determine if the Application performance is acceptable for the defined user load. To quantify the upper limit of the hardware being accessed by the application to determine whether the current system is capable of handling the defined user load. Monitor system components under load

Pre-Requisites for L&P Testing of an Application


Stable system The application and the server(s) it resides on must be absolutely stable. Realistic test environment The test environment should ideally be the QA environment or a close simulation and be dedicated to the load test team for the duration of the test execution. Controlled test environment Load testing requires stability not only in the hardware and software in terms of its reliability and resilience, but also the environment should not be accessed by any other resources during the load test.

Pre-Requisites for L&P Testing of an application (Contd.)


Load testing tool Execution of load testing must be completely automated and requires the tool through out testing period. Ex: Load Runner, QA Load & Silk Performer Business process Identification Business processes for L&P testing has to be identified before starting the scripting activity. Application Data Data required for the identified business process has to be populated before Load Test activity begins.

Factor - Throughput Refers to the number of client requests processed within a certain amount of time. Requests received per hour or operations performed per hour Key factor in determining hardware and system requirements capacity planning

Factor Response Time The delay between point of request and servers response

Network Latency N1 + N2 + N3 + N4 Application Latency A1 + A2 + A3

Factors - Tuning Tuning is a procedure by which product L&P is enhanced Tuning doesnt involve not only touching the code Tuning is done in two levels
Operating system / infrastructure level tuning Application level tuning

Factors Benchmarking & Capacity planning Comparison of two products with L&P factors is called benchmarking The exercise to find out the hardware and s/w requirements for a particular usage/load is called capacity planning

10

How factors influence definition Processes the required number of transactions in any given interval (throughput) Is available and running under different load conditions (availability) Responds fast enough for different load conditions (response time) Delivers worthwhile ROI for the resources hardware & software (capacity planning) Is comparable to and better than that of the competitors (benchmarking)

11

Methodology for L&P testing


Collecting requirements for L&P testing Writing test cases for L&P testing Automating L&P test cases Executing L&P test cases Analyzing L&P test results

12

Collecting Requirements
Basic expectations
Testable (no manual intervention) What factors need to be measured What features to be tested Actual number or % of improvement over comparison need to be stated clearly

How to Derive
- Perf increase compared to previous release - Perf compared to competitive product - Perf compared with actual numbers derived from customer requirements - Perf compared to Architecture / design expectations

13

Writing Test Cases List of Operations or business transactions Clear steps List of OS, product tunable parameters that impact performance testing Loading pattern Resources Expected result Product versions and competitive product versions

14

Automating Test Cases Performance testing is repetitive It is almost impossible to do performance testing without automation The basic need of performance testing is accuracy; manually executing performance test cases introduces inaccuracy There are many factors and tuning parameters for performance testing A very good book keeping (log files, trace files, utilization data . . . Etc)

15

Executing L&P Scripts L&P testing requires less time to execute and enormous time to plan and build environment Data collection is important aspect
Start and end time of test cases execution Log, trace and audit files of both product and OS Utilization of resources Configuration of all environmental factors (HW, SW and security components)

Performance data for individual operations and also scenarios for the customer
16

Analyzing test results Average response time for each transactions Hits per Second Transaction Summary (Passed / Failed) CPU utilization of application & DB servers HTTP Responses Summary Separate data coming from DB with data coming from cache Separate dedicated system Vs background activities
17

L&P Testing Process

18

Typical Web Scenario

19

L&P Test Scenario

20

Conclusion
L&P Testing Will increase uptime and availability of system. Will measure and monitor performance of the business infrastructure. Will avoid project failure by predicting application behavior under defined and increased user loads. Will protect IT investments by predicting scalability and performance. Is the only way to accurately test the end-to-end performance of a system prior to going live

21

L&P Test Process

22

L&P Test Process


Steps
Step 1

Activity
Project Team approaches QC team with Load Testing requirement and the expected deliverables. Project Team also gives an overview of the application for QC Team's understanding and feasibility. QC Team initiates discussion with Project Team about Load Testing process and the input documents required from the Project Team QC Team gives preliminary Effort Estimation to the Project Team (This step may not be applicable for some projects) QC Team sends the following templates to the Project Team to fill in: Business Process Document Scenarios for Load Testing Document Requirement Specification Document

Step 2

Step 3

Step 4

23

L&P Test Process (Contd.)


Steps
Step 5 Step 6

Activity
Project Team fills the documents and sends to QC Team QC Team discusses with Project Team for confirmation on the documents and also for any clarification QC Team prepares the Final Effort Estimation and the Proposal Document and gets approval / acknowledgement from the Project Team (Only on approval of the Effort Estimation, QC Team will start the Load testing activities) QC Team raises Tracker (with Project Team's approval) to admin team to block the Loadrunner Server QC Team gets confirmation from admin team regarding blocking of Loadrunner Server for the Load Testing period

Step 7

Step 8

Step 9

24

L&P Test Process (Contd.)


Steps
Step 10 Step 11

Activity
QC Team prepares the scripts for Load Testing by referring the Business Process Document QC Team raises Tracker (with Project Teams' approval as attachment) asking admin team to monitor the Web Server during the Test Execution period and send the logs to the QC Team QC team informs the time of conducting Load tests to the Project Team so that the Project Team can monitor any other necessary components during the Test Execution period QC Team conducts the Load Tests during the period mentioned in the Tracker Admin team monitors the Web servers during the period of Load Test

Step 12

Step 13

Step 14

Admin team send the logs collected during the Load Test period to the QC Team

25

L&P Test Process (Contd.)


Steps
Step 15

Activity
QC Team prepares the Load Test reports after incorporating the Web Server details collected from admin team QC Team initiates discussion with Project Team to discuss results and also the comparison of the Transaction Response Times between different user loads QC Team sends the Final Load Test Reports and also the Comparison of Transaction Response Times document to the Project Team QC Team sends the VOC template to the Project Team Project Team will send the filled VOC form to the QC Team

Step 16

Step 17

Step 18 Step 19

26

Q&A / Hands-on / Exercise

27

Thank You..

28

Das könnte Ihnen auch gefallen