This page contains a Flash digital edition of a book.
Intellect Software Testing Code of Best Practice 5
Commitment 1:
Requirements and specifications
We will seek to establish with the customer a shared understanding of how
the software should perform, and make every effort to perform and
complete the testing in accordance with that understanding.
We will encourage the customer to make clear We will seek to have the customer provide
their objectives from the perspectives of specifications of how the software under test is
meeting overall business goals and the needs expected to behave both logically and
of the specific testing project. The former can performance-wise. If specifications cannot be
include matters such as upholding a reputation provided then we will work with the customer
for software reliability; the latter might include to ensure that a better understanding of
a requirement to comply with a specified expected behaviour is established, documented
software standard and complete within time, and then used as the basis for testing.
cost, and quality limits.
We appreciate that requirements and
specifications can contain discrepancies as
easily as software can. We will endeavour to
identify and clarify any problems we find in
requirements and specifications.
Commitment 2:
Types and levels of testing
Before commencing testing we will agree the levels and types of testing that
are to be performed.
Testing can be carried out at many different The customer should understand that no
levels within a software development project practical volume of testing can completely
(unit/module, integration, acceptance, eliminate the possibility of faults remaining.
resilience, regression), and can be of many The overall objective is to reduce residual faults
different types (functional, performance, to a level that is both acceptable to all
regression, security, operational acceptance). stakeholders and provides confidence that the
As software testing professionals, we system will support the customer’s business as
endeavour to work with the customer to intended.
ensure that the types and levels of testing
undertaken will best suit the customer’s overall
business and specific objectives.
Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12