Contents Covered:
--------------
Contents Covered:
--------------
Defect/Bug Life Cycle
Test Closure/When To Stop Testing?
Software Testing Metrics
QA/Testing Activities
Principles of Software Testing
Defect/Bug Life Cycle
===========================
state of the defect, in which state defect
are
Test cycle closure
===============================
activities
----------------
==evaluate cycle completion criteria based on time,test coverage,cost,software
critical business objectives,quaity
-prepare test metrics based on the above parameters
--document the learning out of the project
-prepare tet summary report
--qualitative and quantitative reporting of quality of the work product
to the customer
--test result analysis to find out the defect distribution by type
and severity
Deliverables
===============
-test closure report
-test metrics
Test METRICS
******************************
MEASURE/track
test metrics
==========================
defect density
=================
number of defects identifid per requirement
no.of defects found/size(no.of requirements)
defect removal efficiency(DRE)
=================================
(A/A+B)*100
(fixed defects/(fixed defects+missed defects))*100
A---Defects identified during testing/fixed defects
B---defects identified by the customer/missed defects
defect leakage:
===================
no.of defects found in UAT/No of defects found in testing)*100
defect rejection ratio:
=========================
no of defect rejected/total no of defects raised)*100
defect age
===================
fixed date-reported date
customer stisfaction
==============================
no of complaints per period of time
QA/Testing activities:
========================================
--understanding the requirements and functional specifications of the application.
--identifying required test scenario's
--designing test cases to validate application
--setting up test environment(Test bed)
--execute test cases to valid application
--log test results(how many test cases pass/fail)
--defect reporting and tracking
--retest fixed defects of peious build
--perform various types of testing in application.
--reports to test lead about the status of assigned tasks
--participated in regular meetings
--creating automation scripts
--provides recommendaion on whether or not the application/system is ready for
prodution
principles of software testing:
============================================
=======================================
1)start software testing at early stages.means from the beginning
when you get the requirements
2)test the software in order to find the defects
3)Highky impossible to give the bug free software to the customer
4)should not do exhaustive esting.means we should not use same
type of data for testing eery time.
5)testing is context based.means decide what types of testing should
be conduted based on type of application.
6)we should follow the concept of pesticide paadox.
means,if you are executing same cases for longer run,they wont be find any
defects.
we have to keep update test cases in eveery cycle/release
in order to find more defects.
7)we should follow defect clustering.
means some of the modules contains most of the defects.
By experience,we can identify such risky modules.
80% of the problems are found in 20% of the modules.
