a OK this is a gray area. Here??™s a rule. If a tester can always demonstrate the existence of a bug given (say) 10 attempts,
then it exists. It is asking too much to say ???you must be able to demonstrate it at will at every attempt.???
Test Planning and Management 59
??? Dictating what parts of the system should be tested, and when
??“ Stop the developers from imposing new releases on the test team before existing ones were
fully tested
??“ Stop testing when it was evident that the release was useless
??? The testers:
??“ Were poor quality (check their tests, and the descriptions of the bugs they found ??” that??™ll tell
you how poor; see who raised the same bug 20 times with slightly-different wording)
??“ Had too little time or too few tools. Check:
??? How much time was wasted by repetition
??? If the tests are held electronically
??? How long it takes to raise a bug
??“ Had no smoke or regression tests so it was some time before it realized that some features
were missing (ask the testers to show them to you)
??“ Had no smoke tests so it could not immediately reject a release because it lacked essential
features (ask the testers to show them)
??“ Were in a different time-zone to the developers or the users
??“ Were not reviewing their work (review it yourself, and ask the testers to explain the errors you??™ve
found, and why they didn??™t find them themselves). Check the dates the faulty tests were written, and
see if perhaps the testers were simply unmotivated rather than that they had too little time.
Pages:
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189