BUG RESISTANCE

STLC
Software Testing Life Cycle

STLC is a sequence of different activities

performed by the testing team to ensure
the quality of the software or the product.
STLC is an integral part of Software
Development Life Cycle (SDLC). But, STLC
deals only with the testing phases.
BUG RESISTANCE

Manual Testing

Manual testing is a software testing process

in which test cases are executed manually
without using any automated tool.
BUG RESISTANCE
Requirement Analysis: In this phase quality assurance
team understands the requirements like what is to be tested.

Test Planning: Test Planning is most efficient phase of

software testing life cycle where all testing plans are defined. In
this phase manager of the testing team calculates estimated
effort and cost for the testing work

Test Case Development: The test case development

phase gets started once the test planning phase is completed. In

STLC
this phase testing team note down the detailed test cases.

Environment Setup: Basically test environment decides

the conditions on which software is tested. This is independent
activity and can be started along with test case development.

Test Execution: After the test case development and test

environment setup test execution phase gets started. In this
phase testing team start executing test cases based on prepared
test cases in the earlier step.
Test Case Closure: This is the last stage of STLC in which
the process of testing is analyzed.
BUG RESISTANCE

Seven Principles of Testing

Testing Exhaustive Early Defect Pesticide Testing is Absence of

shows the testing is testing clustering paradox context- errors
presence not dependent fallacy
of defects possible
BUG RESISTANCE

REMEMBER

“Absence of
proof is not proof
of absence”
 BUG RESISTANCE

COST of Defects

DETAILS
The cost of defects identified during Software
Testing, completely depends on the impact of the
defects found. The earlier the defect is found, easier
and less costly it is to fix these defects.

For instance, if there is a defect found in the project

requirement specifications and analysis, then it is
relatively cheaper to fix it. Similarly, if the defects or
failures are found in the design of the software,
then the product design is corrected and then re-
issued. However, if these defects somehow get
missed by testers and if they are identified during
the user acceptance phase, then it can be way too
expensive to fix such type of errors.
BUG RESISTANCE
BUG RESISTANCE

Static Testing: Before doing the white box testing done

by the developer what all activities we do that comes under
static testing. It is a part of Verification activity .Here we will
review the code ,review the requirement, well will review the
customer requirement specification, software requirement
specification, high level design, low level design.

Dynamic Testing: Whenever a developer is giving the

build to the test engineers, after giving the build what test
engineers will do it is called Dynamic testing.It is a part of
validation activity. Here we do component testing, system
testing, accepting testing in one word all our functional and
non-functional testing.
BUG RESISTANCE

BLACK BOX
TESTING

Equivalence
Partitioning
Black box testing is nothing but
testing the functionality of an
Boundary Value
Analysis application without actually looking
State Transition
at the code that is called as black box
Testing testing.
Decision
Tables

Use Case based

testing
BUG RESISTANCE

WHITE BOX
TESTING

Statement
Coverage
White box testing is nothing but
testing the internal structure, design
Condition and coding of software which is
Coverage
called as white box testing.
Branch
Coverage

Path Coverage
 BUG RESISTANCE

Scenario-1:: a=3,b=9
Statement Coverage
Statement Coverage is a white box testing technique in
which all the executable statements in the source code
are executed at least once. It is used for calculation of the
number of statements in source code which have been
executed. The main purpose of Statement Coverage is to
cover all the possible paths, lines and statements in
source code.

Scenario-1:: a=-3,b=-9
BUG RESISTANCE

Branch Coverage
Branch coverage technique is used to cover all branches
of the control flow graph. It covers all the possible
outcomes (true and false) of each condition of decision
point at least once. Branch coverage technique is a
whitebox testing technique that ensures that every
branch of each decision point must be executed.
BUG RESISTANCE

Mutation Testing

Mutation testing, also known as code mutation

testing or mutation analysis, is a form of testing in which
we change specific components of an application’s source
code and check whether our tests will fail as a result. We
expect them to fail, as it means that the test suite catches
the bugs when you expect it to. In other words, if you
change your source code and your tests don’t fail, you
didn’t write good tests.
BUG RESISTANCE

GREY BOX
TESTING

Grey Box Testing is a software testing

technique to test a software product or
application with partial knowledge of the
internal structure of the application.