What is Software Testing?

The goal of a Software Tester is to find bugs,

and find them as early as possible and make

sure they get fixed.

The main objective of testing is to

find

defects in requirements, design,

documentation, and code as early as possible.

Why do we test
Software?
To ensure that the Users requirements are

met.
To reduce costly errors.

Five Essentials for Software

Testing
A test strategy that tells what types of testing and

the amount of testing that will work best at finding the

defects that are lurking in the software
A testing plan of the actual testing tasks that is
needed to execute to carry out that strategy
Test cases that have been prepared in advance in the
form of detailed examples to check that the software
will actually meet its requirements
Test data consisting of both input test data and
database test data to use while executing the test
cases
A test environment which is used to carry out
testing.

Taxonomy of Problems in
Testing..
Fault:- In correct step in the program /
module /
component.
Failure:Inability of performing the
function.
Bug:Fault in a program caused by
performance.
Error:- Misunderstanding of the internal
state of the system / Software.
Defect:-External behavior with internal
features.

SDLC vs STLC

Contn..

SDLC vs STLC

What does STLC have?

System Study
Scope/Approach/Estimation
Test Plan Design
Test Case Design
Test Case Review
Test Case Execution
Defect Handling
Deliverables

System
Study
Domain Knowledge :
Banking/Finance/Marketing/Real Estate
others
Software Specifications:

Frontend
Backend

Hardware Specifications:
Hard disk, RAM, Speed, Connectivity of Internet
Number of Days
Number of LOC
Number of Modules

Scope/Approach/Estimati
on
Scope
What is to be tested?
What should not be tested?

Approach
Testing Life Cycle

Estimation
LOC
Number of Test cases
Number of Days to execute Test Cases

Test Plan Design

The document contains:
About the client and the company
Reference Document (SRS, BRS, UIDesign)
Scope
Overview of the application
Testing Approach/Testing Strategy
For each testing type

Definition
Technique
Start Criteria
Stop Criteria

Test Plan Design

contd

Resources and their Roles and Responsibilities

Defect Definition
Risk /Mitigation/Contingency Plan
Training Required
Schedules
Deliverables

Test Case Design

What is a Test Case?

Test case is a description of what to be tested,

what data to be given and what actions to be
done to check the actual result against the
expected result.

Test case contains.

Test Case ID
Precondition
Description
Verification
Author
Status (Pass/Fail)
Remarks

Test Case Format

Contn.
Are Test Cases Reusable?

Yes
Guess the Characteristics of a Good Test Case

TC should be independent
TC should start with What you are Testing
TC should not contain looping and conditional
statements
TC should be uniform

Good Test Cases should

be..
Traceable
No duplicate test cases are allowed
The TC should be updated according to the

release
All Test cases should be executable

Test Case Review

Peer to Peer Reviews
Peer review is a process used for checking the work performed by
one's equals (peers) to ensure it meets specific criteria.

Team Lead Review

Test leaders tend to be involved in the planning, monitoring, and
control of the testing activities and tasks

Team Manager Review

Responsible for the effective development and implementation of
programs to ensure that all information systems products and services
meet minimum company standards and end-user requirements.

Review Process
Take the checklist(list of Tasks)
Take a demo of functionality
Go through Use Cases and Functional

Specifications
Find the gap between the use cases and the
test cases
Submit the review report

Test Case Execution

Execution and its results play an important

role in TESTING.
Each and every activity should have a proof.

Data that is to be
maintained
Number of Test cases executed.
Number of Defects found.
Screen shots of the successful and failure

executions should be taken in a Word

document and should be maintained for future
reference.
Time taken to execute.
Time wasted due to unavailability of the
system.

Test Case Execution

Process

I/O process of Test case

Execution

Inputs

Test Cases
System Availability
Data Availability

Process
Testing the application

Output
Raising the Defects
Save the Results

Defect Handling
What is a Defect?
Defect is a coding error in a program.
It occurs when the application does not

behave in the way it is intended to behave.

It is also famously known as a bug.

How is bug reported?

Bug report format

Bug Life Cycle

Deliverables
All the documents which are prepared in

every stage are to be delivered.

Test Plan
Test Case Design
Test Case Review Report
Test Case Execution Report
Defect Report

Thank You