Software Testing &

Quality Assurance
Software Testing

• A process of analyzing a software item to detect the differences

between existing and required conditions (i.e., defects) and to
evaluate the features of the software item.
Why do we need Software
Testing?
• to evaluate the functionality of a software application

• to find whether the developed software meets the specified

requirements or not

• to identify the defects to ensure that the product is defect-free in

order to produce a quality product.
Software Validation (Dynamic Testing)
• Validation is process of examining whether or not the software satisfies the user
requirements.

• It is carried out at the end of the SDLC.

• If the software matches requirements for which it was made, it is validated.

• Validation ensures the product under development is as per the user requirements.

• Validation answers the question – "Are we developing the product which attempts
all that user needs from this software ?".

• Validation emphasizes on user requirements.

Software Verification (static testing)
• Verification is the process of confirming if the software is meeting the
business requirements, and is developed following to the proper
specifications and methodologies.

• Verification ensures the product being developed is according to

design specifications.

• Verification answers the question– "Are we developing this product

by firmly following all design specifications ?“

• Verifications concentrates on the design and system specifications.

Types of Software Testing
Manual Testing:
• Manual testing is the process of testing the software by hand to learn
more about it, to find what is and isn’t working.
• There are lots of sophisticated tools on the market to help with
manual testing, e.g; Testpad
Automation Testing:
• Automation testing is the process of testing the software using an
automation tool to find the defects.
• Some of the famous automation testing tools for functional testing
include Selenium and Katalon Studio.
Software Testing Approaches
There are three types of software testing approaches.
• White Box Testing
• Black Box Testing
• Grey Box Testing
White Box Testing
• It is also called Glass Box, Clear Box, Structural Testing.

• White Box Testing is based on the application’s internal code

structure.

• In white-box testing, an internal perspective of the system, as well as

programming skills, are used to design test cases.

• Control flow testing (check conditions) and data flow testing (check
declared variables) are the techniques of white box testing.
Black Box Testing
• It is carried out to test functionality of the program.
• It is also called ‘Behavioral’ testing.
• The tester in this case, has a set of input values and respective desired
results.
• On providing input, if the output matches with the desired results, the
program is tested ‘ok’, and problematic otherwise.

Black-box testing techniques

• Boundary values - The input is divided into higher and lower end values. If these
values pass the test, it is assumed that all values in between may pass too.
• Equivalence class - The input is divided into similar classes. If one element of a class
passes the test, it is assumed that all the class is passed.
Testing Levels
• Testing itself may be defined at various levels of SDLC.

• The testing process runs parallel to software development.

• Before jumping on the next stage, a stage is tested, validated and

verified.

• Software Testing Level Includes: Unit testing, integration testing, system

testing, acceptance testing, Regression Testing
Unit Testing

• While coding, the programmer performs some tests on that unit of

program to know if it is error free.

• Testing is performed under white-box testing approach.

• Unit testing helps developers decide that individual units of the

program are working as per requirement and are error free.
Integration Testing

• Even if the units of software are working fine individually, there is a

need to find out if the units if integrated together would also work
without errors.

• Integration Testing is the process of testing the connectivity or data

transfer between a couple of unit tested modules
System Testing
The software is compiled as product and then it is tested as a whole.
This can be accomplished using one or more of the following tests:

• Functionality testing
• Performance testing
• Security & Portability
 Acceptance Testing
• When the software is ready to hand over to the customer it has to go
through last phase of testing where it is tested for user-interaction
and response.

• Alpha testing - The team of developer themselves perform alpha

testing by using the system as if it is being used in work environment.

• Beta testing - After the software is tested internally, it is handed over

to the users to use it under their production environment only for
testing purpose
Regression Testing
• Whenever a software product is updated with new code, feature or
functionality, it is tested thoroughly to detect if there is any negative
impact of the added code.
Software Quality Assurance
• These are software development process monitoring means, by which
it is assured that all the measures are taken as per the standards of
organization.

• This monitoring is done to make sure that proper software

development methods were followed.
Testing Documentation

Testing documents are prepared at different stages

• Before testing
• While being tested
• After testing
Before Testing
• SRS document - Functional Requirements document

• Test Policy document - This describes how far testing should take place before
releasing the product.

• Test Strategy document - This mentions detail aspects of test team,

responsibility matrix and rights/responsibility of test manager and test
engineer.

• Traceability Matrix document - This is SDLC document, which is related to

requirement gathering process.
While Being Tested
• Test Case document - This document contains list of tests required to be
conducted.

• Test description - This document is a detailed description of all test cases

and procedures to execute them.

• Test case report - This document contains test case report as a result of
the test.

• Test logs - This document contains test logs for every test case report.
After Testing
• Test summary - This test summary is collective analysis of all test
reports and logs. It summarizes and concludes if the software is ready
to be launched.
MCQ
• Which of the following is not part of the Test document?

a) Test Case
b) Requirements Traceability Matrix [RTM]
c) Test strategy
d) Project Initiation Note [PIN]
MCQ

• Which term is used to define testing?

a) Evaluating deliverable to find errors

b) Finding broken code
c) A stage of all projects
d) None of the above
MCQ

• Which of the following testing is also known as white-box testing?

a) Structural testing
b) Error guessing technique
c) Design based testing
d) None of the above
MCQ

• Which of the following testing is related to the boundary value

analysis?

a) White box and black box testing

b) White-box testing
c) Black box testing
d) None of the above
MCQ

• What are the different levels of Testing?

a) Integration testing
b) Unit testing
c) System testing
d) All of the above
MCQ
• In which environment we can performed the Alpha testing?

a) User's end
b) Developer's end
c) User's and developer's end
d) None of the above
MCQ

• What is the key objective of Integration testing?

a) Design Errors
b) Interface Errors
c) Procedure Errors
d) None of the mentioned
MCQ

• What is the best time to perform Regression testing?

a) After the software has been modified

b) As frequently as possible
c) When the environment has been modified
d) Both option a & c
MCQ

• In which environment we can performed the Beta testing?

a) User's and developer's end

b) Developer's end
c) User's end
d) None of the above
MCQ

• After which phase, we can proceed to the white box testing?

a) After the coding phase

b) After designing phase
c) After SRS creation
d) After the installation phase
MCQ

• Which of the following is not another name of white box testing?

a) Structural testing
b) Behavioral testing
c) Glass box testing
d) None of the mentioned
MCQ
• The test levels are performed in which of the following order?

a) Unit, Integration, System, Acceptance

b) It is based on the nature of the project
c) Unit, Integration, Acceptance, System
d) Unit, System, Integration, Acceptance
MCQ
• Which of the below testing is related to Non-functional testing?

a) Unit Testing
b) Black-box Testing
c) Performance Testing
d) None of the above
MCQ
• Which of the below testing is related to black-box testing?

a) Boundary value analysis

b) Code path analysis
c) Basic path testing
d) None of the above
MCQ
• Which of the following testing is also called Acceptance testing?

a) Beta testing
b) White-box testing
c) Grey box testing
d) Alpha testing
MCQ
-------- testing is used to check the code?

a) Grey box testing

b) Black box testing
c) White-box testing
d) Red box testing
MCQ
• What is the full form of SRS?

a) Software respond system

b) Software requirements specification
c) System responds software
d) System requirements specification
MCQ
• Which of the following testing technique can be used in order to
determine the validation test?

a) Black-box Testing
b) White-box Testing
c) Yellow- box Testing
d) All of the above
MCQ
------ testing is a testing technique where the actual data verified in the
real environment.

a) Regression Testing
b) Alpha Testing
c) Beta Testing
d) None of the above
MCQ

The following statement is related to which of the below options:

• "It determines the quality of processes used to create a quality
product. It is system of management activities, and preventive
process. It applies for entire life cycle and deals with process?"

a) Quality control
b) Validation
c) Verification
d) Quality Assurance