Scribd
Upload
86 views

By: Chankey Pathak Chankey007@gmail - Co M

The document provides an overview of software testing concepts and processes. It discusses the importance of testing in the software development life cycle and defines key terms like errors, bugs, faults, and failures. The testing life cycle and various testing types - like unit testing, integration testing, system testing, and regression testing - are explained. The roles of testers, test leads, and test managers in the testing team are outlined. Quality assurance and quality control processes are also summarized.

Uploaded by

Davis Michael
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
86 views

By: Chankey Pathak Chankey007@gmail - Co M

The document provides an overview of software testing concepts and processes. It discusses the importance of testing in the software development life cycle and defines key terms like errors, bugs, faults, and failures. The testing life cycle and various testing types - like unit testing, integration testing, system testing, and regression testing - are explained. The roles of testers, test leads, and test managers in the testing team are outlined. Quality assurance and quality control processes are also summarized.

Uploaded by

Davis Michael
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 44

http://www.technostall.

com

By: Chankey Pathak


[email protected]
m

Agenda:

Introduction
Importance of testing in SDLC
Testing life cycle
Test planning
Types of testing
Verification & Validation
Quality Assurance & Control
Bug reporting

Software Testing
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 positive
and
negative conditions by manual or
automated means. It checks for the : Specification
Functionality
Performance

Why Software
Testing
?
Software Testing is important as it
may cause mission failure, impact
on operational performance and
reliability if not done properly.
Effective software testing delivers
quality
software
products
satisfying users requirements,
needs and expectations.

What ????
is

an ERROR??

.is a Bug??
.is Fault, Failure ??

Bug, Fault & Failure


A person makes an Error
That creates a fault in software
That can cause a failure in operation
Error
: An error is a human action that produces the
incorrect result that
results in a fault.
Bug
: The presence of error at the time of execution of
the software.
Fault

: State of software caused by an error.

Failure : Deviation of the software from its expected result.


It is an event.

Who is a
Software Tester??..
Software Tester is the one who
performs testing and find bugs, if they
exist in the tested application.

The Testing Team


Program Manager

The planning and execution of the project to ensure the


success
of a project minimizing risk throughout the lifetime of the
project.
Responsible for writing the product specification,
managing the schedule and making the critical decisions
and trade-offs.

QA Lead

Coach and mentor other team members to help improve


QA effectiveness
Work with other department representatives to
collaborate on
joint projects and initiatives

Test Analyst\Lead Responsible for planning, developing and executing


automated test
systems, manual test plans and regressions test plans.
Identifying the Target Test Items to be evaluated by the
test effort
Defining the appropriate tests required and any
associated Test
Data
Gathering and managing the Test Data
Evaluating the outcome of each test cycle

Test Engineer Writing and executing test cases and Reporting defects
Test engineers are also responsible for determining the
best way a
test can be performed in order to achieve 100% test
coverage of all

When to Start
Testing in SDLC

Requirement
Analysis
Design
Coding
Testing
Implementation
Maintenance

Testing starts from Requirement


Phase

Testing
Life
Cycle
Project Initiation
System Study

Summary Reports
Analysis

Test Plan
Regression Test
Design Test Cases

Report Defects

Execute Test Cases


( manual /automated )

Test
Plan
A test plan is a systematic approach to testing a
system i.e. software. The plan typically contains a
detailed understanding of what the eventual testing
workflow will be.

Test
Case
A test case is a specific procedure of
testing a particular requirement.
It will include:
Identification of specific
requirement tested
Test case success/failure criteria
Specific steps to execute test
Test Data

Unit
Testing

1.
2.

3.

Test each module individually.


Follows a white box testing (Logic of
the program)
Done by Developers

Integration Testing
After completing the unit
testing and dependent modules
development, programmers
connect the modules with
respect to HLD for Integration
Testing through below
approaches.

System Testing
After completing Unit and Integration testing
through white box testing techniques
development team release an .exe build (all
integrated module) to perform black box
testing.

Usability Testing
Functional Testing
Performance Testing
Security Testing

Usability Testing
During this test, testing team concentrates on the user
friendliness of build interface. It consists of following sub tests.

User Interface Test: Ease of use (screens should be


understandable to operate by End User)

Look & Feel :- attractive


Speed in interface :- Less number of task to complete
task

Manual Support Test :- Context sensitiveness of user


manual.

Functional
Testing

The process of checking the


behavior of the application.

It is geared to functional
requirements of an application.
To check the correctness of
outputs.
Data validation and Integration
i.e. inputs are correct or not.

Performance
Testing

LOAD TESTING Also Known as Scalability Testing.


During this test, test engineers execute application build
under customer expected configuration and load to estimate
performance.
STRESS TESTING During this test, Test engineers
estimates the peak load. To find out the maximum number of
users for execution of out application user customer
expected configuration to estimate peak load.
PEAK LOAD > CUSTOMER LOAD (EXPECTED)
DATA VOLUME TESING -- Testing team conducts this test
to find the maximum limit of data volume of your
application.

Security Testing
Testing how well the system
protects against
unauthorized internal or
external access, willful
damage, etc, may require
sophisticated testing
techniques

Smoke testing
Smoke testing is nonexhaustive software
testing, ascertaining that
the most crucial functions
of a program work, but not
bothering with finer details.

Alpha Testing
1. The application is tested by the users who
doesnt know about the application.
2. Done at developers site under controlled
conditions
3. Under the supervision of the developers.

Acceptance
Testing

A formal test conducted to determine whether


or not a system satisfies its acceptance criteria
and to enable the customer to determine
whether or not to accept the system.
It is the final test action before deploying the
software. The goal of acceptance testing is to
verify that the software is ready and can be
used by the end user to perform the functions
for which the software was built.

Beta Testing
1. This Testing is done before
the final release of the
software to end-users.
2. Before the final release of the
software is released to users
for testing where there will
be no controlled conditions
and the user here is free
enough to do what ever he
wants to do on the system to
find errors.

Regression
Testing
Testing with the intent of
determining if bug fixes have
been successful and have not
created any new problems.
Also, this type of testing is
done to ensure that no
degradation of baseline
functionality has occurred.

Monkey Testing
Testing the application randomly
like hitting keys irregularly and
try to breakdown the system
there is no specific test cases and
scenarios for monkey testing.

Verification
Verification is the process
confirming that -software meets
its specification, done through
inspections and walkthroughs

Use To identify defects in the


product early in the life cycle

Validation
Validation is the process
confirming that it meets the
users requirements. It is the
actual testing.

Verification : Is the Product


Right
Validation : Is it the Right
Product

What is Quality ?
Quality is defined as meeting the customers
requirements and according to the standards
The best measure of Quality is given by FURPS
Functionality
Usability
Reliability
Performance
Scalability

Why
Quality ?
Quality

is the important
factor affecting an
organizations long term
performance.
Quality improves
productivity and
competitiveness in any
organization.

Quality Assurance
Quality Assurance is a planned
and systematic set of activities
necessary to provide adequate
confidence that products and
services will conform to
specified requirements and
meets user needs.
It is process oriented.
Defect prevention based.
Throughout the Life Cycle.
Its a management process.

Quality Control
Quality control is the
process by which product
quality is compared with
the applicable standards
and the action taken when
non conformance is
detected.
It is product oriented
Defect detection based

QA vs. QC

Quality Assurance makes


sure that we are doing the
right things, the right Way.
QA focuses on building in
quality and hence
preventing defects.
QA deals with process.

Quality Control makes sure


the results of what weve
done are what we expected .
QC focuses on testing for
quality and hence detecting
defects.
QC deals with product.

QA is for entire life cycle.

QC is for testing part in


SDLC.

QA is preventive process.

QC is corrective process.

Bug Life Cycle

Tester finds the bug


and report it to Test Lead

Bug

Test Lead confirms


that it is a valid Bug

New
Deferred

Assigned
Resolved

Re-open

Verified
Closed

When to Stop Testing


Cost No. of Bugs

Cost incurred
Stop Testing

Bugs ratio

Amount of Testing

You might also like