What is The Fundamentals of Software Testing? - Part 2
Please refer to part 1 before reading any further!
Evaluating exit criteria and reporting:
The test “exit criteria” (established during “Test planning and control”) indicate that testing is complete.
Test closure activities:
- Ensure that all documentation has been correctly completed
- Close down and archive the test environment, infrastructure and testware
- Hand over testware to maintenance team
- Log lessons learned
The psychology of testing:
Selecting the appropriate individual(s) to perform the tests, and communicating the results of the tests to the developers, requires a basic understanding of the psychology of testers and developers.
The ISEB Software Testing guidance provides a hierarchy of ‘independence’ – that is, a list of individuals who could potentially test the software, gradated according to their perceived level of detachment from the development process:
- The authors of the code
- Members of the same development team as the authors of the code
- A different group within the same organization
- A different organization
There are varying advantages and disadvantages to individuals at different levels in the hierarchy performing the software tests. For example, the developer might be able to resolve a difficulty more quickly, but might be also be less likely to spot the difficulties in the first place.
In addition to the independence/detachment of the testers from the software development process, it is important to consider how testers can communicate the results of the test to the developers. The ISEB Software Testing Foundation exam requires students to explain strategies for providing courteous feedback on defects, for example:
- Focus on delivering quality, rather than pointing out mistakes;
- Test reports are not directed towards people but towards products;
- Discuss problems openly, and attempt mutual understanding;
- At the end of a discussion, confirm that both parties understand what has been agreed.