University Institute of Engineering

DEPARTMENT OF COMPUTER SCIENCE &

ENGINEERING
Subject Name: Software Engineering
Subject Code: 23CST-206
Software Testing

Er. Jagmeet Kaur

E8387
ASSISTANT PROFESSOR DISCOVER . LEARN . EMPOWER
CSE

09/12/24 Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh Univer 1

sity
 Chapter-7
Software Testing
• Validation Testing

• System Testing

Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 2

 Validation Testing

• The process of evaluating software during the development process or

at the end of the development process to determine whether it satisfies
specified business requirements.
• Validation Testing ensures that the product actually meets the client's
needs. It can also be defined as to demonstrate that the product fulfills
its intended use when deployed on appropriate environment.
• It answers to the question, Are we building the right product?

Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 3

 Validation Testing

• Validation Testing, carried out by QA professionals, is to determine if

the system complies with the requirements and performs functions for
which it is intended and meets the organization’s goals and user needs.
• This kind of testing is very important, as well as verification testing.
• Validation is done at the end of the development process and takes
place after verification is completed.

Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 4

 Validation Testing

• Thus, to ensure customer satisfaction, developers apply validation

testing.
• Its goal is to validate and be confident about the product or system and
that it fulfils the requirements given by the customer.
• The acceptance of the software from the end customer is also its part.

Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 5

 Validation Testing

• When software is tested, the motive is to check the quality regarding

the found defects and bugs.
• When defects and bugs are detected, developers fix them. After that,
the software is checked again to make sure no bugs are left.
• In that way, the software product’s quality scales up.

Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 6

 Validation Testing

• The aim of software testing is to measure the quality of software in

terms of a number of defects found in it, the number of tests run and
the system covered by the tests.
• When bugs or defects are found with the help of testing, the bugs are
logged and the development team fixes them.
• Once the bugs are fixed, testing is carried out again to ensure that they
are indeed fixed and no new defects have been introduced in the
software.
• With the entire cycle, the quality of the software increases.

Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 7

Validation Testing - Workflow
• Validation testing can be best demonstrated using V-Model. The
Software/product under test is evaluated during this type of testing.

Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 8

Activities

• Unit Testing
• Integration Testing
• System Testing
• User Acceptance Testing

Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 9

Validation Testing Variations:
• Component/Unit Testing – The aim of the unit testing is to look for bugs in the software
component. At the same time, it also verifies the work of modules and objects which can
be tested separately.
• Integration testing- This is an important part of the software validation model, where the
interaction between the different interfaces of the components is tested. Along with the
interaction between the different parts of the system, the interaction of the system with the
computer operating system, file system, hardware, and any other software system it might
interact with, is also tested.
• System testing- System testing is carried out when the entire software system is ready.
The main concern of system testing is to verify the system against the specified
requirements. While carrying out the tests, the tester is not concerned with the internals of
the system but checks if the system behaves as per expectations.
• Acceptance testing- During this testing, a tester literally has to think like the client and
test the software with respect to user needs, requirements, business processes and
determine whether the software can be handed over to the client or not.
Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 10
Validation Testing Variations:
• Alpha testing- This type of testing is done at the developers’ site by
potential customers/users. Any problems encountered during this
testing are rectified by the developers then and there.
• Beta testing- Once the software passes the alpha testing stage, beta
testing is done at the user’s end.
• Regression testing- This testing is done after the desired changes or
modifications are made to the existing code. The code, when put to
test, may have certain errors that can be resolved by making essential
changes. The software is again put to test after these changes are made
to check whether the new code fulfils customer requirements or not.

Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 11

Stages of Validation testing Process
• Validation Planning – To plan all the activities that need to be included while
testing.
• Define Requirements – To set goals and define the requirements for testing.
• Selecting a Team – To select a skilled and knowledgeable development team
(the third party included).
• Developing Documents – To develop a user specification document
describing the operating conditions.
• Estimation/Evaluation – To evaluate the software as per the specifications
and submit a validation report.
• Fixing bugs or Incorporating Changes – To change the software so as to
remove any errors found during evaluation.
Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 12
System Testing
• System Testing is a type of software testing that is performed on a
complete integrated system to evaluate the compliance of the system
with the corresponding requirements.
• In system testing, integration testing passed components are taken as
input.
• The goal of integration testing is to detect any irregularity between the
units that are integrated together.
• System testing detects defects within both the integrated units and the
whole system. The result of system testing is the observed behavior of
a component or a system when it is tested.
Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 13
System Testing
• System Testing is carried out on the whole system in the context of
either system requirement specifications or functional requirement
specifications or in the context of both.
• System testing tests the design and behavior of the system and also the
expectations of the customer. It is performed to test the system beyond
the bounds mentioned in the software requirements specification (SRS).
• System Testing is basically performed by a testing team that is
independent of the development team that helps to test the quality of
the system impartial. It has both functional and non-functional testing.
• System Testing is a black-box testing.
Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 14
System Testing
• System Testing is performed after the integration testing and before
the acceptance testing.

Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 15

System Testing Process

Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 16

System Testing Process
• Test Environment Setup:
Create testing environment for the better quality testing.
• Create Test Case:
Generate test case for the testing process.
• Create Test Data:
Generate the data that is to be tested.
• Execute Test Case:
After the generation of the test case and the test data, test cases are
executed.

Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 17

System Testing Process
• Defect Reporting:
Defects in the system are detected.
• Regression Testing:
It is carried out to test the side effects of the testing process.
• Log Defects:
Defects are fixed in this step.
• Retest:
If the test is not successful then again test is performed.

Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 18

Types of System Testing

• Usability Testing- mainly focuses on the user's ease to use the application,
flexibility in handling controls and ability of the system to meet its objectives
• Load Testing is necessary to know that a software solution will perform under
real-life loads.
• Regression Testing involves testing done to make sure none of the changes
made over the course of the development process have caused new bugs. It also
makes sure no old bugs appear from the addition of new software modules over
time.
• Recovery testing is done to demonstrate a software solution is reliable,
trustworthy and can successfully recoup from possible crashes.

Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 19

Types of System Testing

• Migration testing- is done to ensure that the software can be moved from
older system infrastructures to current system infrastructures without any
issues.
• Functional Testing - Also known as functional completeness
testing, Functional Testing involves trying to think of any possible missing
functions. Testers might make a list of additional functionalities that a
product could have to improve it during functional testing.
• Hardware/Software Testing - IBM refers to Hardware/Software testing as
"HW/SW Testing". This is when the tester focuses his/her attention on the
interactions between the hardware and software during system testing.

Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 20

 References

• [Link]
STING%20is%20a%20level,a%20larger%20computer%2Dbased%20sys
tem
.
• [Link]
• [Link]
on_testing.htm#:~:text=Software%20Testing%20%2D%20Validation%
20Testing,actually%20meets%20the%20client's%20needs
.
• [Link]

Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 21

THANK YOU

Er. Jagmeet Kaur, Asst. Prof., CSE, Chandigarh University 22