•
Repeatable — so that others can
easily carry forward the process that has
been defined.
•
Improvable — such that each build becomes more
efficient in producing defects and issues.
The goal of this measurable and improvable
process is to produce more defects and
issues in the testing lifecycle so that less
are found in production.
• Measurable
— such that the test effort can be
quantifiable. How many defects are found in
each stage? What is the trend and levels of
severity of the defects? How close is the
testing cycle to completion? How long does a
transaction take to complete? How many
concurrent users? Do transactions meet the
Service Level Agreement performance goals?
What is the threshold for network
throughput?
•
Manageable
— such that the project can be decomposed
into modular, defined tasks
• Automated
— to implement tests that take advantage of
the best-of-breed testing software that
tests client-side application functionality,
network architecture, web and application
servers, communication protocols, operating
system measurements, and database servers.
•
Risk-based
— by targeting test types, application
functionality and architectural components
that are the most crucial to the usage of
the application(s). RTTS utilizes a
risk-based approach to testing and ranks
strategies and test targets by assessing the
risk to the client of not performing various
test types and strategies.
|
