C3 Testing and reviewing software solutions Application of processes and techniques to test and review software and ensure
a solution is fit for purpose.
•
Use of functional requirements, non-functional requirements and key
performance indicators to inform testing.
•
Develop an initial testing schedule to plan what should be tested and when,
including coverage of (as appropriate to the solution):
o
module testing
o
integration testing
o
automated testing
o
user testing and feedback.
•
Write test plans and apply appropriate unit test cases (UTCs), including:
o
use of success criteria and KPIs to inform testing
o
identification of the test to be carried out
o
description of the purpose of the test
o
identification of test data to be used (if required) (e.g. valid, valid extreme,
invalid, invalid extreme and erroneous).
•
Execute UTCs and document results, including:
o
recording any errors generated
o
describing the program outcomes
o
comparing test outcomes to expected outcomes
o
describing any additional actions required.
•
Rework the code and UTCs to fix identified defects.
•
Record corrective actions for identified defects.
•
Key stakeholders from whom to seek feedback on a product:
o
the client
o
software development team, (e.g. line mangers and other developers)
o
test users.