The document details the software testing process, emphasizing its importance in identifying software bugs to prevent costly or dangerous issues. It outlines the software testing life cycle (STLC) and various methodologies, including static and dynamic testing, as well as functional and non-functional testing. The document also describes different testing levels, techniques, and concludes that effective testing is essential for producing defect-free software.

1. Software Testing
Presented By : Rohit Raj Singh

2. Introduction
 Software Testing is a process, used to identify
the correctness, completeness and quality of
developed computer software.
 It is the process of executing a
program/application under a positive or negative
condition by manual or automated means.
 It Checks for the-
 Functionality
 Performance

3. Why is Software Testing Important?
 It is important because software bugs could be
expensive or even dangerous.
 In April 2015, Bloomberg terminal in London
crashed due to software bug affected more than
3bn traders on financial markets.

4. Objectives
 Uncover as many as error or bug as possible in a
given product.
 Validate the quality of a software testing using
minimum cost and efforts.
 Generate high quality test cases, perform
activity test and issue correct or helpful problem
reports.

5. Error, Bug & Failure
 Error - It is a human action that produced
incorrect result.
 Bug - The presence of error at the time of
software exaction.
 Failure – The deviation of the software from its
expected result.

6. Software Testing Life Cycle (STLC)
 STLC is the testing process which is executed in
systematic and planned manner.
 STLC is defined as a sequence of activities
conducted to perform Software Testing.
 Let’s quickly see what all activities are involved
in typical Software Testing Life Cycle.

7. Phases of Software Testing Life Cycle

8. Test Planning
 A test plan is a detailed document that outlines
the Test Strategy, Test Objective and Resources
(manpower, software, hardware) required for test
schedule and estimation.

9. Test Case Development
 It specifies the procedure of testing to a
particular requirement. It includes-
 Identification of specific requirement.
 Criteria of success and failure.
 Specific step to execute the test.
 Test Data (Inputs/Output).

10. Testing Methodologies
 Software Testing Methodology is defined as
strategies and testing types used to certify that,
the application under testing meets the client
expectations.
 Each testing methodology has a defined test
objective, test strategy.
 Software Testing has static and dynamic testing
to validate the software product.

11. Various Testing Methodologies

12. Static Testing
 Static Testing, a software testing technique in
which the software is tested without executing
the code. It has two parts analysis and review.
 Analysis - The code written by developers are
analyzed (usually by tools) for structural defects
that may lead to bugs.
 Review - Typically used to find and eliminate
errors or ambiguities in documents such as
requirements, design, etc.

13. Dynamic Testing
 Dynamic Testing, is a kind of software testing in
which the software should be compiled &
executed.
 Parameters such as Memory Usage, CPU Usage,
Response Time and Overall Performance of the
software are analyzed.
 Dynamic Testing is further classified in two main
categories, on the basis of software functionality.
 Functional Testing
 Non-Functional Testing

14. Functional Testing
 Functional Testing, is a type of software
testing where the system is tested against the
functional requirements and specifications.
 Functional Testing are tested by feeding the
input and examining the output.
 It ensures that the requirements are properly
satisfied the software application or not.
 Functional Testing is divided in two type of
testing-
 White Box Testing
 Black Box Testing

15. Levels of Functional Testing
There are four different level of functional testing
used in testing process.
 So, each level of testing aim to test the different
aspect of the system.
 Four Levels of testing are -----
 Unit Testing
 Integration Testing
 System Testing &
 Acceptance Testing

16. White Box Testing
 It is also called Glass Box/Clear Box/Structural
testing
 White Box testing based on internal prospective
of the system, and programming skills are used to
design test case for testing.
 Testing is based on internal code structure of the
application.
 Testing usually done at Unit Level Testing.

17. Unit Testing
 Unit Testing, is a level of software testing where
individual units/components of a software are
tested.

18. Code Coverage
 Code Coverage is a technique to measure how
much the test covers the software and how much
part of the software is not covered under
the test.

19. Statement Coverage
 Statement Coverage is a technique, which is used
to calculate and measure the number
of statements in the source code which have
been executed.

20. Branch Coverage
 Branch Coverage is a technique, which aims to
ensure that each one of the possible branch from
each decision point is executed at least once and
thereby ensuring that all reachable code is
executed.

21. Path Coverage
 Path Coverage refers to designing test cases such
that all linearly independent paths in the program
are executed at least once.

22. Black Box Testing
 It is software testing method in
which testing evaluates the
functionality of the software under
the test without looking at the
internal code structure.
 Test are based on requirement and
functionality.

23. Black Box Testing Techniques
 They are given below ---
 Equivalence Partitioning
 Boundary Value Analysis
 Decision Table
 State Transition

24. Equivalence Partitioning
 It is a software testing technique that divides the
input test data of the application under test into
each partition at least once of equivalent data
from which test cases can be derived.

25. Boundary Value Analysis
 Boundary Value Analysis is based on testing the
boundary values of valid and invalid partitions.

26. Decision Table
 Decision Table testing technique is appropriate
for functionalities which has logical relationships
between inputs.

27. State Transition
 State Transition testing, we pick test cases from
an application where we need to test different
system transitions.

28. Integration Testing
 In integration Testing, individual software modules
are integrated logically and tested as a group.
 A typical software project consists of multiple
software modules, coded by different programmers.
integration Testing focuses on checking data
communication among these modules.
 Hence it is also termed as 'I & T' (Integration and
Testing), 'String Testing' and sometimes 'Thread’.

29. Smoke/Sanity Testing
 This Testing is performed after a software build to
ascertain that the critical functionalities of the
program are working fine. It is executed before
any detailed functional or regression tests are
executed on the software build.

30. Functionality Testing
 Functionality testing is performed to verify that a
software application performs and functions
correctly according to design specifications.

31. Regression Testing
 Regression testing is the process
of testing changes to computer programs to make
sure that the older programming still works with the
new changes.

32. System Testing
 System Testing is a technique, performed to
evaluate the complete system and the system
compliance against specified requirements.
 In System testing, the functionalities of
the system are tested from an end-to-end
perspective.

33. Acceptance Testing
 Acceptance Testing is a level of software
testing where a system is tested for acceptability.
 Alpha & Beta Testing are the type of Acceptance
Testing.

34. Alpha Testing
 Alpha Testing is a type of acceptance testing,
performed to identify all possible issues/bugs
before releasing the product to everyday users or
the public.
 Alpha Testing is carried out in a “Lab
Environment” by the “Testers or Internal
Employees” of the organization.

35. Beta Testing
 Beta Testing of a product is performed by “Real
Users” of the software application in a “Real
Environment” and can be considered as a form of
external User Acceptance Testing.

36. Conclusion
 In order to be cost effective, testing must be
concentrated on areas where it will be most
effective.
 Testing usually related to the faults remaining
from earlier stage, that can lead to a heavy
distraction.
 Testing is just a process in order to make your
software application defect free.

37. Thank You