software testing genius

Rehearsal of LoadRunner in 1 Hr-Interview Questions 71-80

Welcome to “Software Testing Genius”. Subscribe to my RSS feed for latest content on Software Testing.

Rehearsal of LoadRunner in 1 Hr: Interview Questions 71 – 80

While appearing in an interview for a position on HP LoadRunner, do a quick rehearsal of your knowledge on this tool.

Here is a collection of 80 short questions on LoadRunner & Load-Testing, the Test Managers commonly use while interviewing new aspirants for their organization.

The entire rehearsal of these questions can take less than an hour.

Set of Ten Questions

Q.71: Estimating Target Load Levels

Once you have identified the current load levels, the next step is to understand as accurately and as objectively as possible the nature of the load that must be generated during the testing.

Using the current usage figures, estimate

how many people will visit the site per week/month or day. Then divide that number to attain realistic peak-hour scenarios.

It is important to understand the volume patterns, and to determine what load levels your web site might be subjected to (and must therefore be tested for).

There are four key variables that must be understood in order to estimate target load levels:

1) How the overall amount of traffic to your Web site is expected to grow

2) The peak load level which might occur within the overall traffic

3) How quickly the number of users might ramp up to that peak load level

4) How long that peak load level is expected to last

Once you have an estimate of overall traffic growth, you’ll need to estimate the peak level you might expect within that overall volume.

<<<<<< =================== >>>>>>

Q.72: How do we estimate the Test Duration?

The duration of the peak is also very important. A Web site that may deal very well with a peak level for five or ten minutes may crumble if that same load level is sustained longer than that.

You should use the length of the average user session as a base for determining the load test duration.

<<<<<< =================== >>>>>>

Q.73: What is Ramp-up Rate?

As mentioned earlier, Although your site may be handling x number of users per day, only a small percentage of these users would be hitting your site at the same time.

Therefore, when preparing your load test scenario, you should take into account the fact that users will hit the website at different times, and that during your peak hour the number of concurrent users will likely gradually build up to reach the peak number of users, before tailing off as the peak hour comes to a close.

The rate at which the number of users build up, the "Ramp-up Rate" should be factored into the load test scenarios (i.e. you should not just jump to the maximum value, but increase in a series of steps).

<<<<<< =================== >>>>>>

Q.74: How to create the scenarios that are to be used to load test the web site?

The information gathered during the analysis of the current traffic is used to create the scenarios that are to be used to load test the web site.

The identified scenarios aim to accurately emulate the behavior of real users navigating through the Web site.

For example, a seven-page session that results in a purchase is going to create more load on the Web site than a seven-page session that involves only browsing. A browsing session might only involve the serving of static pages, while a purchase session will involve a number of elements, including the inventory database, the customer database, a credit card transaction with verification going through a third-party system, and a notification email. A single purchase session might put as much load on some of the system’s resources as twenty browsing sessions.

Similar reasoning may apply to purchases from new vs. returning users.

A new user purchase might involve a significant amount of account setup and verification something existing users may not require.

The database load created by a single new user purchase may equal that of five purchases by existing users, so you should differentiate the two types of purchases.

<<<<<< =================== >>>>>>

Q.75: How to prepare a script to run each scenario with the number of types of users concurrently playing back to give you a load scenario?

Using the load test tool, write the scripts to run each scenario with the number of types of users concurrently playing back to give you a load scenario.

The key elements of a load test design are:

1) Test objective
2) Pass/fail criteria
3) Script description
4) Scenario description

Load Test Objective:

The objective of this load test is to determine if the Web site, as currently configured, will be able to handle the X number of sessions/hr peak load level anticipated. If the system fails to scale as anticipated, the results will be analyzed to identify the bottlenecks.

Pass/Fail Criteria: The load test will be considered a success if the Web site will handle the target load of X number of sessions/hr while maintaining the pre-defined average page response times (if applicable). The page response time will be measured and will represent the elapsed time between a page request and the time the last byte is received.

Since in most cases the user sessions follow just a few navigation patterns, you will not need hundreds of individual scripts to achieve realism—if you choose carefully, a dozen scripts will take care of most Web sites.

<<<<<< =================== >>>>>>

Q.76: How To Create a Load Testing Scenario?

Scripts should be combined to describe a load-testing scenario. A basic scenario includes the scripts that will be executed, the percentages in which those scripts will be executed, and a description of how the load will be ramped up.

By emulating multiple business processes, the load testing can generate a load equivalent to X numbers of virtual users on a Web application. During these load tests, real-time performance monitors are used to measure the response times for each transaction and check that the correct content is being delivered to users. In this way, they can determine how well the site is handling the load and identify any bottlenecks.

The execution of the scripts opens X number of HTTP sessions (each simulating a user) with the target Web site and replays the scripts over and over again. Every few minutes it adds X more simulated users and continue to do so until the web site fails to meet a specific performance goal.

<<<<<< =================== >>>>>>

Q.77: Why System Performance Monitoring Is Important?

It is vital during the execution phase to monitor all aspects of the website. This includes measuring and monitoring the CPU usage and performance aspects of the various components of the website, i.e. not just the web-server, but the database and other parts as well (such as firewalls, load balancing tools etc.)

You can quote following examples:

1) One e-tailor, whose site fell over (apparently due to a high load), when analyzing the performance bottlenecks on their site discovered that the web-server had in fact only been operating at 50% of capacity. Further investigation revealed that the credit card authorization engine was the cause of failure - it was not responding quick enough for the website, which then fell over when it was waiting for too many responses from the authorization engine. They resolved this issue by changing the authorization engine, and amending the website coding so that if there were any issues with authorization responses in future, the site would not crash.

2) Another e-commerce site found that the performance issues that they were experiencing were due to database performance issues, while the web-server CPU usage was only at 25%, the backend db server CPU usage was 86%. Their solution was to upgrade the db server.

Therefore, it is necessary to use (install if necessary) performance monitoring tools to check each aspect of the website architecture during the execution phase.

<<<<<< =================== >>>>>>

Q.78: Could You Suggest an Execution Strategy for a Load Scenario?

Start with a test at 50% of the expected virtual user capacity for 15 minutes and a medium ramp rate. The different members of the team [testers will also need to be monitoring the CPU usage during the testing] should be able to check whether your website is handling the load efficiently or some resources are already showing high utilization.

After making any system adjustments, run the test again or proceed to 75% of expected load. Continue with the testing and proceed to 100%; then up to 150% of the expected load, while monitoring and making the necessary adjustments to your system as you go along.

<<<<<< =================== >>>>>>

Q.79: How To Report Load Testing Results?

Often the first indication that something is wrong is the end user response times start to climb. Knowing which pages are failing will help you narrow down where the problem is.

Whichever load test tool you use, it will need to produce reports that will highlight the following:

1) Page response time by load level

2) Completed and abandoned session by load level

3) Page views and page hits by load level

4) HTTP and network errors by load level

5) Concurrent user by minute

6) Missing links report, if applicable

7) Full detailed report which includes response time by page and by transaction, lost sales opportunities, analysis and recommendations

<<<<<< =================== >>>>>>

Q.80: What are the Important Aspects of Website Load Testing?

When testing websites, it is critically important to test from outside the firewall. In addition, web-based load testing services, based outside the firewall, can identify bottlenecks that are only found by testing in this manner.

Web-based stress testing of web sites is therefore more accurate when it comes to measuring a site's capacity constraints.

Web traffic is rarely uniformly distributed, and most Web sites exhibit very noticeable peaks in their volume patterns. Typically, there are a few points in time (one or two days out of the week, or a couple of hours each day) when the traffic to the Web site is highest.

Full Set of 80 Questions

Rehearsal of QTP in 1 Hr. Interview Questions

Largest Database of Sample Papers - 1060 Unique Questions
for Practice Just before the ISTQB Foundation Exam


ISTQB Foundation Exam - Full Crash Course for Download


ISTQB Advanced CTAL Test Analysts Exam - Full Crash Course for Download


ISTQB Advanced CTAL Test Manager Exam - Full Crash Course for Download


What Successful Testers say about the Quality of this website

If you want to keep track of further articles on Software Testing,
I suggest you to subscribe my
RSS feed
.

You can also Subscribe by E-mail
and get All New articles delivered directly to your Inbox.

Full Study Material for Popular Certification Exams:

Study Material - HP QTP & QC Certification Exam

Study Material - ISTQB Certification Exam

Study Material - HP LoadRunner Certification Exam

Study Material - IBM RFT Certification Exam

Consolidated Study Material - Testing & QA


Most Popular Topics in Demand:

Practical Roadmap to QTP Certification

Practical Roadmap to ISTQB Certification

Practical Roadmap to CSTE Certification

General HR Interview Questions Common For All 

Tricky HR Interview Questions Common For All
 

Rehearsal of QTP in 1 Hr. -  Interview Questions

 

Comments :

1 comments ↓

# 1 dpreddy on 2012-11-08 16:10:57
i am beginner in load runner suffering alot in server side analysis. So, i want server analysis expert to learn. Pls help me urgently.



Leave Your Comments: (*) Marked Fields are Mandatory

You can apply basic formatting to the text

Name *
 
Email Address *
 
Website
 
Speak your mind
characters
sex hikayeleri