Book Review: Lessons Learned in Software Testing
Kishore Chavali
This is a recent book authored by leaders in Software Testing: Cem Kaner, James Bach and Bret Pettichord. This book is divided into 11 Chapters and contains around 290 simple lessons every software tester can read and implement. I bought this book recently and started reading the same. On Amazon.com it is available at 30% reduced price and this may be right time to buy this book. Click here to go to Amazon.com for this item.
Sample Extract: The following is a sample from the
book:
Lesson 5: Find Important
Bugs Fast
Most likely, your mission includes finding bugs that are important (as opposed to insignificant) and finding them quickly. If so, what does this mean in terms of the tests you run?
· Test things that are changed before things that are the same. Fixes and updates mean fresh risk.
· Test core functions before contributing functions. Test the critical and the popular things that the product does. Test the functions that make the product what it is.
· Test capability before reliability. Test whether each function can work at all before going deep into the examination of how any one function performs under many different conditions
· Test common situations before esoteric situations. Use popular data and scenarios of use.
· Test common threats before exotic threats. Test with the most likely stress and error situations.
· Test for high-impact problems before low-impact problems. Test the parts of the product that would do a lot of damage in case of failure.
· Test the most wanted areas before areas not requested. Test any areas and for any problems that are of special interest to someone else on the team.
You will also find important problems sooner if you know more about the product, the software and hardware it must interact with, and the people who will use it. Study these well.