software testing book code example

Example 1: what makes good test engineer

A good test engineer has a 'test to break'
 attitude, an ability to take the point of 
 view of the customer, a strong desire for
 quality, and an attention to detail. 
 Tact and diplomacy are useful in maintaining
 a cooperative relationship with developers, 
 and an ability to communicate with both 
 technical (developers) and non-technical
 (customers, management) people is useful.
 Previous software development experience
 can be helpful as it provides a deeper
 understanding of the software development process,
 gives the tester an appreciation for
 the developers' point of view, and reduce
 the learning curve in automated test tool
 programming. Judgement skills are needed 
 to assess high-risk areas of an application
 on which to focus testing efforts when 
 time is limited.

Example 2: when to do manual testing

-Unstable test cases
-Tests that you will only run only once.
-The only exception to this rule is that
if you want to execute a test with a very large 
set of data, even if it’s only once,
then it makes sense to automate it.
-Unfinished functionality
-Visual test cases
-Also Tests that need to be run ASAP
which usually a new feature which is
developed requires a quick feedback
so testing it manually at first making sense.