Scribd
Upload
73 views5 pages

7 Testing Principles: Correctness, Completeness, and Quality Actual Results Match The Expected Results

The document outlines 7 key testing principles: 1) Testing shows the presence of defects, not their absence. 2) Exhaustive testing of even the simplest program is impossible. 3) Testing should start as early as possible in the development cycle. 4) Defects tend to occur in clusters, so removing one defect often helps find others.

Uploaded by

Spring
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
73 views5 pages

7 Testing Principles: Correctness, Completeness, and Quality Actual Results Match The Expected Results

The document outlines 7 key testing principles: 1) Testing shows the presence of defects, not their absence. 2) Exhaustive testing of even the simplest program is impossible. 3) Testing should start as early as possible in the development cycle. 4) Defects tend to occur in clusters, so removing one defect often helps find others.

Uploaded by

Spring
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Correctness, completeness, and quality

Actual results match the expected results

7 TESTING PRINCIPLES

Principle 1

Testing shows presence of defects

Principle 2

Exhaustive testing is impossible

Principle 3

Early Testing

Principle 4

Defect Clustering

Principle 5

Pesticide Paradox

Principle 6

Testing is context dependent

Principle 7

Absence of errors - fallacy

STLC

STLC Stage

Entry Criteria

Requirement Requirements
Analysis
Document available
(both functional and
non functional)
Acceptance criteria
defined.

Activity

Analyse business functionality to


know the business modules and
module specific functionalities.
Identify all transactions in the
modules.
Identify all the user profiles.

Application
Gather user interface/authentication,
architectural document geographic spread requirements.
available.
Identify types of tests to be
performed.
Gather details about testing priorities
and focus.
Prepare Requirement Traceability
Matrix (RTM).
Identify test environment details
where testing is supposed to be
carried out.
Automation feasibility analysis (if

Exit Criteria

Deliverables

Signed off RTM

RTM

Test automation
feasibility report
signed off by the
client

Automation
feasibility report
(if applicable)

required).

Test Planning Requirements


Documents
Requirement
Traceability matrix.
Test automation
feasibility document.

Analyze various testing approaches Approved test


available
plan/strategy
document.
Finalize on the best suited approach
Effort estimation
document signed
Preparation of test plan/strategy
document for various types of testing off.

Test
plan/strategy
document.
Effort estimation
document.

Test tool selection


Test effort estimation
Resource planning and determining
roles and responsibilities.

Test case
Requirements
development Documents
RTM and test plan
Automation analysis
report

Create test cases, automation scripts Reviewed and


(where applicable)
signed test
Cases/scripts
Review and baseline test cases and
scripts
Reviewed and
signed test data
Create test data

Test cases/scripts
Test data

Test
System Design and
Understand the required architecture, Environment setup Environment
Environment architecture documents environment set-up
is working as per ready with test
setup
are available
the plan and
data set up
checklist
Prepare hardware and software
Environment set-up
requirement list
Smoke Test
plan is available
Test data setup is Results.
Finalize connectivity requirements complete
Prepare environment setup checklist Smoke test is
successful
Setup test Environment and test data
Perform smoke test on the build

Accept/reject the build depending on


smoke test result

Test
Execution

Baselined RTM, Test Execute tests as per plan


Plan , Test case/scripts
are available
Document test results, and log
defects for failed cases
Test environment is
ready
Update test plans/test cases, if
necessary
Test data set up is done
Map defects to test cases in RTM
Unit/Integration test
report for the build to Retest the defect fixes
be tested is available
Regression testing of application

All tests planned


are executed

Defects logged and


tracked to closure Test cases
updated with
results

Track the defects to closure

Test Cycle
closure

Testing has been


completed
Test results are
available
Defect logs are
available

Evaluate cycle completion criteria Test Closure report


based on - Time, Test coverage , Cost signed off by client
, Software Quality , Critical Business
Objectives
Prepare test metrics based on the
above parameters.
Document the learning out of the
project
Prepare Test closure 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

Completed RTM
with execution
status

Defect reports

You might also like