no independent testers to establish and maintain the integrity of the products of the software

independent testers within development identified

independent test team version controlled

independent testers from the business tracked for changes

levels of independence all items of testware are
for usability, security etc configuration management related to each other
independent test specialists for testing, it may mean
and related to development items
independent testers outsourced or so that traceability can be maintained
external to the organisation
all documents and software items are referenced
unambiguously in test documentation
independent testers see other and different defects
are unbiased benefits of independence
test organisation
the chance of an event, hazard, threat or situation occurring
verify assumptions made during development
risk and its undesirable consequences
isolation from the development team a potential problem
testing may be the bottleneck as the last checkpoint
drawbacks of independence determined by the likelihood of an adverse event happening
developers may lose a sense of
responsibility for quality the level of risk and the impact (the harm resulting from that event)
risk = impact x probability
test leader / test manager
roles within a test team
tester the risks that surround the project’
s capability to deliver its objectives
project risks

to give feedback and visibility about test activities potential failure areas (adverse future events or hazards) in the system
product risks
test case preparation a risk to the quality of the product
percentage of work done
test environment preparation
risk & testing to decide where to start testing
risks are used
number of test cases run / not run and where to test more
test case execution Test Management
test cases passed / failed
to reduce the risk of an adverse effect occurring
testing is used
defect density to reduce the impact of an adverse effect
defects found and fixed
defect information provides feedback about the residual risk
failure rate common test metrics risk based testing a risk-control activity
by measuring the effectiveness of critical defect removal
retest results test progress monitoring

test coverage of requirements, risks or code reduce the levels of product risk

subjective confidence of testers in the product starts at the beginning of a project

a risk-based approach to testing
dates of test milestones identifies product risks

the cost of running the next test uses them to guiding testing
testing costs test progress monitoring & control
versus the benefit of finding the next defect
discrepancies between actual & expected outcomes
what happened during a period of testing one objective of testing is to find defects
need to be logged as incidents
analysed information and metrics report the state of testing
from discovery and classification
recommendations and decisions about future actions should be tracked
to correction and confirmation of the solution
any guiding or corrective actions
during development
taken as a result of information and
metrics gathered and reported during review
incident management may be raised at any time
making decisions based on information during testing
why record them
from test monitoring
test control
during use of a software product
re-prioritise tests when an identified risk occurs
change the test schedule typical test control actions issues in code

developers must test defect fixes they may be raised for anything the working system
set an entry criterion
any type of documentation

© SQS Group Ltd.