SOFTWARE TESTING LOKESH JOEL
QUALITY: Quality is defined as not only the justification of the requirement or absence of the Defects but
also the Presence of the value
DEFECT: It is defined as deviation from the requirement
Steps: The steps to be following to refine the product
1. IDENTIFICATION OF THE DEFECTS
2. ISOLATION OF THE DEFECTS
3. SUBJECTING THESE DEFECTS FOR RECTIFICATION
Ensure that all the defects raised are rectified and making sure that the
product is defective
TESTING: It is defined as the process in which defects are IDENTIFIED,ISOLATED,SUBJECTED FOR
RECTIFICATION and Ensure that the product is defect free in order to provide the quality to the product
and hence customer satisfaction
Note: Defect rectification is also known as BUG FIXING
SOFTWARE DEVELOPMENT LIFE CYCLE: SDLC is a systematic scientific process with multiple sequential
phases in it to make sure that the project development is affective
1. INITIAL PHASE 2. ANALYSIS PHASE
3. DESIGN PHASE 4. CODING PHASE
5. TESTING PHASE 6. DELIVERY & MAINTENANCE PHASE
Each phase has 4 activities
1. TASKS/RESPONSIBILITES 2. ROLE
3. PROCESS 4. DOCUMENTS
1. INITIAL PHASE :
TASKS/RESPONSIBILITES Requirement gathering
Business Analyst
ROLE
Engagement Manager
PROCESS To make sure that the work is properly done(own life cycle)
DOCUMENTS BDD/BD/FRS/BRS
HIGH LEVEL INFORMATION Given by client
BDD
LOW LEVEL INFORMATION
Functional Requirement (use cases)
Business Rules
Use case: It is defined as the description of functionality Screen Shorts
of an application in terms of actor actions and Templates
Corresponding responses
2. ANALYSIS PHASE: INPUT : BDD
OUTPUT: SRS
Analyzing The Requirements
Feasibility Study
TASKS/RESPONSIBILITES Gap Analysis
Tentative Project Planning
System Requirement Analysis
ROLE System Analyst
PROCESS How to work (To make sure that the work is properly done(own life cycle))
DOCUMENTS SRS (SYSTEM REQUIREMENT SPECIFICATION DOCUMENT)
SOFTWARE TESTING LOKESH JOEL
2. DESIGN PHASE
INPUT : SRS
OUTPUT: TDD
HLD (HIGH LEVEL DOCUMENT)
TASKS/RESPONSIBILITES
LLD (LOW LEVEL DOCUMENT)
CHIEF ARCHITECT
ROLE
TECHNICAL LEAD
PROCESS To make sure that the work is properly done(own life cycle)
DOCUMENTS TDD
HLD: overview of the project(eg., How many module of a project can be divided etc)
LLD: is given in detailed ( eg., How many sub-module or how many units in a single module etc)
CONTENTS OF TDD:
1. DEPICTION DESCRITION + PICTURE
2. FLOW CHARTS
3. DIAGRAMS
CLASS DIAGRAMS
4. DFD (DATA FLOW DIAGRAM)
OBJECT DIAGRAMS
5. PSEUDO CODE
ACTIVITY DIAGRAMS
SEQUENCE DIAGRAMS
STATE DIAGRAMS
COMPONENT DIAGRAMS
3. CODING PHASE
INPUT : TDD
OUTPUT: SCD
TASKS/RESPONSIBILITES PROGRAMMING/ DEVELOPING
ROLE PROGRAMMER/ DEVELOPER
PROCESS CODING STANDARDS
DOCUMENTS SCD(SOURCE CODE DOCUMENT)
CODING STANDARDS: As per the development team is concerned they will be given guidelines
primary known as coding standards. The coding standards are guidelines to the development to
ensure for the proper programming
4. TESTING PHASE
TASKS/RESPONSIBILITES TESTING
ROLE Test Engineer
REVIEW OF BDD, TP, MTD, FPD etc.
PREPARATION OF REVIEW REPORT(RR)
SENDING THE RR TO THE AUTHOR FOR THE CLARIFICATION
PROCESS PREPARATION OF THE TEST CASE DOCUMENT
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
STLC
DOCUMENTS TCD
STLC (SOFTWARE TESTING LIFE CYCLE):
In order to make sure that the testing process is more systemic and effective
STLC is adopted and following which has the following phases
1. TEST PLANNING 2. TEST DEVELOPMENT /DESIGN
3. TEST EXECUTION 4. RESULT ANALYSIS
5. BUG TRACKING 6. REPORTING
SOFTWARE TESTING LOKESH JOEL
1. TEST PLANNING:
It is defined as a strategic document that describes how to carry on the testing on the
entire application efficiently and with almost optimization to provide a quality to the
product
Contents of the TEST PLAN:
Objective / Scope of Testing
Functionalities that are to be Tested
Functionalities that are not to be Tested
Resource Planning
Scheduling
Test Strategy
Test deliverables
Test Terminology and defect metrics definition
Areas to be Automated and Areas not to be Automated
Evaluation of automated tools and Selection of them (list of the automated
tools used)
Risks and Contingency plans
Entry criteria and Exit criteria
Approval authority information
ROLE: SOFTWARE QUALITY MANAGER ,QUALITY LEAD will preparing the Test Plan
The input Document / Base Document for preparing the Test Plan is PROJECT
PLAN which is prepared by PROJECT MANAGE
2. TEST DEVELOPMENT /DESIGN :
The development /Design is nothing but building the strategy of testing in terms of
preparation of Test Case Document
It has following fields
1. TEST In this field the test engineer has to describe what and all the functionalities are to be tested
OBJECTIVE/SCOPE precisely (VERIFY & VALIDATE THE MODULE NAME)
The testing when exactly the testing takes place has to be documented
For GUI testing
While Accessing
2. TEST SCENARIO
1.xxxxx
For functional
2.xxxxxx
The testing is to be planned to be performed in such a way that the specific functionality can be
tested in terms of
1. GUI Testing (To test the look & feel of the Application with GUI Test Cases under GUI
Testing
3. TEST PROCEDURE
2. +Ve Testing(To test the Positive Behavior of the Application with +Ve Test Cases under
functional Testing
3. -Ve Testing(To test the Negative Behavior of the Application with -Ve Test Cases under
functional Testing
4. TEST CASES Following table can be used for TEST CASE PREPARATION
TEST CASE USE CASE EXPECTED ACTUAL
DESCRIPTION RESULT SEVERITY PRIORITY
NO REF VALUE VALUE
5. TEST DATA:
6. TEST EXECUTION:
7. RESULT ANALYSIS:
SOFTWARE TESTING LOKESH JOEL
8. BUG TRACKING: (lly DEFECT PROFILE DOCUMENT)
ASSIGN TO
DATA STEPS
STATUS
DEFECT MODULE VERSION BUILD SEVERI PRIORI
DESCRIPTION SUBMITTER OF TO BE
NO NAME # # TY TY
SUBMISSION REPRODUCED
9. REPORTING: (TEST REPORT DOCUMENT)
SEVERITY: It is defined as an expression that expresses how serious the defect is
FATAL, MAJOR, MINOR, SUGGESTION
PRIORITY: It is defined as an expression/note/message to the development team to define the
sequence for the defects for the process of rectification.
o In other word it tells the developer what defects are to be taken first, next and last for the
defect rectification
CRITICAL, HIGH, MEDIUM, LOW
HOLD
AS PER DESIGN
NO
REQUIREMENT TESTER’S ERROR
DEVELOPMENT IS IT DEFFECT
REALLY RECTIFIRD
MOD1
YES RECTIFICATION
OPEN/
TESTING
NEW
FIXED FOR
RECTIFICATION
IS THERE ANY
NO STOP
DEFFECT
BUG STATUS:
REOPEN NEW/OPEN
FIXED FOR
IS THE DEFFECT RECTIFICATION
CLOSED
REALLY RECTIFIRD CLOSED
REOPEN
HOLD
AS PER DESIGN
5. DELIVERY & MAINTENANCE PHASE: TESTER’S
In this phase once the project is completely tested, it will be certified ERROR
and delivered to the customer.
Even after delivery while usage if something goes wrong with the product still the services are
extended under maintenance as per the deal of the company.
SOFTWARE TESTING LOKESH JOEL
TEST CASE: It is an opportunity to get a defect or it is an opportunity to check the functionality of an
application
There are three types. They are
1. GUI based Test Cases
2. Functional Based Test Cases
3. Input based Test Cases
1. Guidelines for GUI Test Cases:
Look for all the features that are present in the screen (AVAILABILITY)
Check for look and feel of various objects with respect to Alignment, objects,
overlaps, colors etc.
Check for the consistency
Check for the Spelling of the text present in the screen
2. Functional Based Test Cases :
These Test Cases are generated based on the functional requirements
These Test Cases are divided into Two Categories
1. +Ve Test Cases
2. -Ve Test Cases
3. Input Based Test Cases :
Derived based on some techniques like
1. Boundary value Analysis (BVA)
2. Equal Call Partitioning (ECP)
3. Error Guessing
