Effective Software Testing -
50 Specific Ways to Improve Your Testing
Author: Elfriede Dustin
Paperback: 304 pages
Publisher: Addison-Wesley Pub Co
ISBN: 0201794292
Effective Software Testing lists 50 specific ways to improve your testing. The book is for both Manual and Automation testers, and is broken down into the following chapters.
Summaries of some of the topics covered:
A mistake that most software development houses make is not involving the testing team right from the
beginning of a project. Verification of requirements and the implementation of Test procedures must be
put in place right from the inception of a project. Communication with regards to requirement changes
must be highly enforced to ensure that all responsible are aware of any changes. Development must not
be based on the existing system.
Understanding the Task at hand and the related testing goal is imperative to a project. Risks must be
taken into account as major delays could occur as a result. The acquisition of good testing data and
planning the test environment are discussed. Estimates form a big part testing, for example, estimates
on test preparation and execution time.
The testing team is made up of different types of people with many different capabilities and expertise
and, as such, roles need to be defined along with the person's responsibilities. Tester's evaluations
and effectiveness must also be measured.
When creating test cases the following must be kept in mind: What should be tested, When should test
procedures be developed, How should test procedures be designed, Who should develop the tests. The use
of test procedure templates and test design standards must be used for repeatability, consistency and
completeness of testing. Test cases must be derived from requirements. Test procedures are ever changing
and testers must be fully aware of such changes. Proven testing techniques must be used when designing test
case scenarios. When compiling test cases, it must be kept in mind that the test case must be generic and
specific data must not be used. A separate document must be kept with such data. Well thought out exploratory
testing must also be performed to ensure greater coverage.
Personal Opinion:
Elfriede Dustin has written a very informative book, which can be used by Testers in the know who wish to structure their testing efforts further, as it provides a deeper insight into testing. Automated Testing is also covered giving the tester knowledge of both manual and automated testing practices.
The book is written in such a way, however, that it becomes tedious to read. When picking up the book one would like to go straight into the "meat" of the subject, however the author has made the pre-amble of the book far too long.
Junior testers without much experience and knowledge of testing terminology may be confused by the terms used. The book does not contain a Glossary nor does it contain enough examples to provide the reader with visuals to back up the information.
Testing will vary from tester to tester and from system to system, however the following must be kept in mind: Adhering to proven test methodologies where possible will ensure a successful testing effort.
Alex Gonçalves