DEPARTMENT OF INFORMATION TECHNOLOGY

SUBJECT:SOFTWARE TESTING AND AUTOMATION

YEAR:III SEM:VI SEC:A&B

PART-A

1.what is Volume Testing

Volume testing comes under software testing. It helps us to check the behavior
of an application by inserting a massive volume of the load in terms of data is
known as volume testing.

In volume testing, we will concentrate on the number of data rates than the
number of users. It is also called Flood testing.

2.Why do we need the volume testing?

Before we understand the need for volume testing, we will see one example of
volume testing.

Suppose there is an e-commerce web application, which is generally used by

1000 end-users. And during the sale or festive season, on the web application,
around 40-50k users try to access the web application.

And the application will crash, or the data could not load successfully, which
cause problems for the customers.

3. What is Recovery Testing

Recovery testing is testing where the test engineer will test the application to
check how well the Software or the application recovers from disasters or
crashes.

It is one of the most important types of non-functional testing categorized

under performance testing.

While executing the recovery testing, we should first take the backup and save it
to a secured location to keep away from any data loss if the data is not
recovered successfully.

4.Why recovery testing is important?

The recovery testing is significant if we are developing the application for a

user who will decides the difference between success and failure for our
organization.

Therefore, we need to develop software, which has enough consistency and

recoverability.

PART-B

1. DISCUSS BRIEFLY ABOUT LOAD TESTING.

Load testing:
In software testing, load testing is an integral part of performance testing
under non-functional testing.

Load testing is testing where we check an application's performance by

applying some load, which is either less than or equal to the desired load.

Here, load means that when N-number of users using the application
simultaneously or sending the request to the server at a time.
Generally, load testing is used to signify how many concurrent users handle the
application and the application's scale in terms of hardware, network capacity etc.

The Objective of Load Testing

The main objective of using the load testing is to fulfill the following aspects:

o The load testing is used to perform the maximum quantity of software

applications without important performance breakdown.
o It is used to govern the scalability of the application and allows various
users to access it.
o It is used to identify the total count of users that can access the
application simultaneously.
o The load testing is used to determine whether the latest infrastructure can
run the software application or not and determine the sustainability of the
application concerning extreme user load.

Load Testing Process

The Load testing process will be completed in the following steps:

Step1: Test environment setup

o In the first step, we will set up the test environment to execute the load
testing to ensure the testing can be done appropriately.
o And the test environment should be set up near to the production
environment as likely in terms of network, hardware, software specifications etc.

Step2: Load the test scenario or specify the performance criteria

o In the next step, we will define the performance criteria, which contain
the response time, reasonable limits on throughput, and the load test
transaction.
 o And then, we create the load test scenarios, which ensure the success
criteria are finalized.
o In the load testing, transactions are decided for an application
and data is set for each transaction.

Step3: Execution of test scenarios

o Once we successfully create the load test scenarios, we will execute the
particular test scenarios.
o But before we execute the load test scenarios, we have to set the different
configurations and matrices to collect the information.
o The load on the server is matched by consecutively several virtual users
to complete the tasks concurrently.
o And we can execute the entire scenario in virtual user groups or
individual virtual users.

Step4: Analysis of the test result

o After executing the load test scenarios, we will analyze the test results.
o The load test Scenario can be inspected with the help of LoadRunner online
monitors like:
o System resource
o Run-time transaction
o Network delay
o Web resource

Step5: Re-test

o The last step of the load testing process depends on the test result because
if the test fails, we have to perform the same process repeatedly until the
test result is passed and all the issues and bottlenecks are fixed.

Examples of Load Testing

More people have a habit of booking a flight ticket throughout holidays or on

the days when an air company has an offer.

As we can see, more people incline to buy products during a promotional event
like Diwali, Black Friday, big billion days sales.
And if a website or an application crashes in such an event, users may leave the
website and go to a competitor's application, leading to loss of revenue and
market share. Those scenarios may occur because we do not perform the load
testing on the system.

Load testing tools

o LoadNinja
o Apache JMeter
o NeoLoad
o HP Performance Tester
o WebLoad
o LoadView

Advantages and disadvantages of load testing

Advantages

Some of the vital benefits of performing the load testing are as follows:

o Load testing helps us to detect the bottlenecks and performance-related

issues before production.
o The load testing enhances the scalability regarding network, software and
database for the system or software application.
o The major advantage of performing the load testing is reducing the cost
failures, which also helps us minimize the system interruption risks.
o Customer's satisfaction is enhanced while using the load testing.

Disadvantages

Following are the drawbacks of load testing:

o Load testing can only be executed if we have enough knowledge of any

programming language as well as testing tools.
o Usage of load testing tools can be an expensive process because pricing
depends on the number of virtual users supported.

2. EXPLAIN ABOUT STRESS TESTING

Stress testing:
In software testing, stress testing is an important part of performance testing
under non-functional testing.

Stress Testing is testing used to check the accessibility and robustness of

software beyond usual functional limits. It mainly considers for critical software
but it can also be used for all types of software applications.

It is also known as Endurance Testing, fatigue testing or Torture Testing.

The stress testing includes the testing beyond standard operational size,
repeatedly to a breaking point, to get the outputs.

It highlights the error handling and robustness under a heavy load instead of
correct behavior under regular conditions.

Why do we need to perform the Stress Testing?

o When the system is under stress, it should display a proper error message.
o To inspect whether the system works under bizarre circumstances.
o If the system is failed under risky situations could result in huge profits
loss.
o By implementing Stress Testing, we will be prepared for extreme
conditions.

Example : Education Board's result website

Stress testing is important to perform on the education board's result website.

On the day of some results, many students, users, and applicants will logins to
the particular to check their grades.

Therefore, the execution of stress testing helps identify the failure of the
application and evaluate the performance and recoverability when the ultimate
load occurs in a short duration or when the result is out.

Types of Stress Testing

Stress testing can be categories into various parts, which are as follows:
o Product or Application stress testing
o Server-client or distribute Stress Testing
o Analytical Stress Testing
o Systematic Stress Testing
o Transactional Stress Testing

o Server-client Stress Testing: Server-client stress testing also known as

distributed stress testing is carried out across all clients from the server.
o Product Stress Testing: Product stress testing concentrates on
discovering defects related to data locking and blocking, network issues,
and performance congestion in a software product.
o Transactional Stress Testing: Transaction stress testing is performed
on one or more transactions between two or more applications. It is
carried out for fine-tuning and optimizing the system.
o Systematic Stress Testing: Systematic stress testing is integrated
testing that is used to perform tests across multiple systems running on
the same server. It is used to discover defects where one application data
blocks another application.
o Analytical Stress Testing: Analytical or exploratory stress testing is
performed to test the system with abnormal parameters or conditions
 that are unlikely to happen in a real scenario. It is carried out to find
defects in unusual scenarios like a large number of users logged at the
same time or a database going offline when it is accessed from a
website.
o Application Stress Testing: Application stress testing also known as
product stress testing is focused on identifying the performance
bottleneck, and network issues in a software product.
Stress Testing Process
The stress testing process is divided into 5 steps:
1. Planning the stress test: This step involves gathering the system data,
analyzing the system, and defining the stress test goals.
2. Create Automation Scripts: This step involves creating the stress testing
automation scripts and generating the test data for the stress test scenarios.
3. Script Execution: This step involves running the stress test automation
scripts and storing the stress test results.
4. Result Analysis: This phase involves analyzing stress test results and
identifying the bottlenecks.
5. Tweaking and Optimization: This step involves fine-tuning the system
and optimizing the code with the goal meet the desired benchmarks.
6.

Stress testing tools

As we know that stress testing is part of performance testing, the tools used
for performance testing can be used for stress testing.Therefore, we have
various types of Stress testing tools available in the market, where some are
commercial tools and open-source tools. Some of the most commonly Stress
testing are listed below:

o Apache JMeter
o NeoLoad
o Stress tester
o LoadRunner

Advantages and disadvantages of Stress Testing

Advantages

Some of the vital benefits of performing Stress testing is as follows:

o Stress testing signifies the system's behavior after failure and makes sure
that the system recovers quickly from the crashes.
o The most important advantage of executing the stress testing will make
the system work in regular and irregular conditions in a suitable way.
o It determines the scalability and enhance the performance of the software.

Disadvantages

Some of the most common drawbacks of Stress testing are as follows:

o Even in open-source tools like JMeter, a load testing environment is

required, which should be as close to the production environment setup as
possible.
o If we are writing the Stress test script, the person should have enough
scripting knowledge of the language supported by the particular tool.
o If we are using stress testing, it will require additional resources, which
makes this testing bit costlier.
o If we perform the Stress Testing manually, it became a tedious and
complicated task to complete, and it may also not produce the expected
results.