Book Review: Software Bug Stories

By -
As James Clear, Author of Atomic Habits says: "Habits that have a high rate of return in life: Reading Every Day"

I thought I would start small in reading a book every day, and then read a post from Ajay Balamurugadas that the book is released on May 1st 2020.

Book Review: Software Bug Stories
Authors: Ajay Balamurugadas and Saranya Easwaran

This book should be read by anyone involved in building or testing the software. This book comes in electronic format (PDF/EPUB).
This book took couple of hours for me to read and learn from it.



I heard about this book from Saranya, when I met her at one of the workshop. 
Concept looked simple when I heard about it. But after reading the book I realized a lot of hard work to make this book a reality.

The Summary of the book inspired to read it.
"Bugs are everywhere. What can we learn about them. Ajay and Saranya analyze twenty such bugs and present to you a collection of bug stories."

We always face bugs at our projects we have tested and customers reported the bugs.

The stories in the book are divided into 4 sections
1. Simple but Costly Bugs
2. Bugs affecting Personal Life
3. Loss of Lives and Financial
4. Credibility of Organizations

This book summarizes the below points for each bug:
a. What Happened  (Summary of the Real Time Bug)
b. The Bug        (The cause of the bug)
c. Impact         (User Impact, Financial Impact etc)
d. Testing Lesson  (This is important aspect from this book)
e. Other References 

Few months back, I learned - When we report the Bugs:
Our Bugs should not only say about technical/functional impact. It should also refer to "How it impacts the End User"

Analyse the bug which you find in production or reported by customers
a. what is the root cause of the bug. 
b. How it escaped to Production.
c. What could be the contributing factors.
d. Modeling the application, gives us risks to other areas.


I recommend that you buy/read this book, learn from it and share with your team members (or) friends.

Popular Posts

JMeter Producing Error: Windows RegCreateKeyEx(...) returned error code 5

By -
After running JMeter.bat on Command Line, Problem java.util.prefs.WindowsPreferences <init> WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5. Cause Environment Resolving the problem The error occurs because java.util.prefs.WindowsPreferences is trying to save information in HKEY_LOCAL_MACHINE\Software\JavaSoft\Prefs instead of under HKEY_CURRENT_USER\Software\JavaSoft\Prefs. Windows 7 64-bit The work around is to Open JMeter.bat file as the administrator and so it creates the key HKEY_LOCAL_MACHINE\Software\JavaSoft\Prefs.
Read more

Understanding about Contract Testing

By -
Image
Yesterday Morning (9th May 2020), I had good discussion with  Sundaresan  Krishnaswami on " Contract Testing ". I thank  Sundaresan   for his time and sharing his knowledge. It started with an example: The Owner provides the house or Place of Residence to the Tenants. "Rent Agreement" is provided for the house and It contains agreement to use the house. The house comes with like kitchen, living room, bed room, fans, geysers etc.. It also contains who resides and what is the contractual period, obligation (money) etc.. Here, Owner is the Server and Tenant is Client.                                         Client-Server Architecture. Illustrating the same in the E-Commerce Context: In Some Development Companies, There can be two teams developing the Payments and Orders APIs. In B2B or B2C Ecommerce applications, we place an order using web browser through payment methods and Order is created. Order is successful only when Payment is successful. In general, Payments te
Read more