The document discusses different types of software testing. It states that software testing is a process that verifies that a system meets requirements and finds errors. There are two main types of testing: whitebox testing, where internal code structure is known, and blackbox testing, where it is unknown. Whitebox testing is used for verification while blackbox testing is used for validation from an end user perspective. The document also outlines various stages of testing like unit testing, integration testing, and functional testing.

1. Software Testing
Savyasachi Sharma

2.  Software is a set of instructions stored digitally
within the computers memory , which tells the
computer system what to do.

3.  Testing is the process of executing a program
with the intention of finding errors .

4.  Software testing is a process that should be
done during the development process. In other
words software testing is a verification and
validation process.

5.  Verification is the process to make sure the
product satisfies the conditions imposed at the
start of the development phase.
 to make sure the product behaves the way we
want it to.

6.  validation is the process to make sure the
product satisfies the specified requirements at
the end of the development phase.
 To make sure that the product is built as per
customer requirements.

7. Verification is to check
whether the software
conforms to specifications
Its does not involve
executing the code
It is human based checking
of documents and files
Verification is done by
development team to provide
that the software is as per the
specification
Verification
Validation is to check
whether the software meet
the customer requirements
Its always involves executing
the code.
Its computer based
execution of program
Validation is carried out wit
the involvement of client and
testing team
validation

8.  Testing Verifies that the system meets the
different requirements including, functional,
performance Security usability and so on .

9. There are two basics of software testing
 Whitebox Testing
 Blackbox Testing

10. • Whitebox testing is software testing method in
which the internal structure of the item being
tested is known to the tester
• Whitebox testing is often used for verification

11.  Testing can be commenced at and earlier stage.
One need not wait for the GUI to be available
 Testing is more thorough, with the possibility of
covering most paths.
 The other advantage of whitebox testing is that it
helps in optimising the code

12.  As knowledge of code and internal structure is a
prerequisite, a skilled tester is needed to carry
out this type of testing, which increases the cost
 Not looking at the code in a run time
environment.

13.  Blackbox testing is a software testing method
in which the internal structure of the item
being tested is not known to the tester.
 Blackkbox testing is often used for Validation.
 Blackbox testing is done by the professional;
testing team.

14.  Tester can be non technical.
 Tester needs no knowledge of implementation
including specific programming languages
 Test will be done from an end users point of
view. Because end user should except the
system

15.  Not all properties of a software product can be
tested
 The region for a failure is not found.
 Only a small number of possible inputs can be
tested and many program paths will be left
untested.

16. There are many types of testing like,
 Unit Testing
 Integration Testing
 Functional Testing
 System Testing
 Stress Testing

17.  Acceptance Testing
 Regression Testing
 Beta testing
 Performance Testing
 Usability Testing

18.  Unit testing is that validate individual unit of
source code working properly.
 Unit is smallest testable part an application.
 Mostly done by developers of the moudules

19.  To isolate each part of program and show that
individual part are correct

20.  Unit Testing reduces the level of bugs in
production code.
 Unit testing inspire confidence
 Unit Testing makes it easier to change and
refactor code

21.  Unit Testing will not catch every error in the
programme. By definition it only test the
functionality of the units.

22.  Integration Testing is testing in which a group of
components are combined to produce output.
 Also the interaction between software and
hardware is tested in integration testing if
software and hardware components have any
relation.

23.  Prerequisite of integration Testing -
 Before we being integration testing it is
important that all the component have been
successfully unit tested.

24.  To discover faults that are due to incorrect
interaction between different software module.

25.  Top – Down Integration testing
 Bottom Integration testing.

26.  Top Down Integration testing as the term
suggest , starts always as the top of the program
hierarchy and travels towards its branches.

27. Module 1
Module 2 Module 3
Module 6Module 5Module 4

28.  Bottom up Integration testing as its name implies
starts at the lowest level in the program structure

29. Module 1
Module 2 Module 3
Module 6Module 5Module 4

30.  Functional testing is the testing to ensure that the
specified functionality required in the system
requirements work.
 It is not concerned about the source code of the
application.

31. What do you test in functional testing
 The Prime objective of functional testing is
checking the functionalities of the software
testing
 Mainline functions - Testing the main functions
of an application.
 Basic usability – it involves basic usability
testing of the system it checks if user can freely
navigate through the screens without any
difficulties.

32.  Accessibility – Checks the accessibility of the
system for the user.
 Error Conditions – Usage of testing techniques
to check for error conditions. It checks wheather
suitable error messages are displayed.