A Testers Journey

An ounce of practice is better than tons of theory

Why-Why Analysis

This is not post which will say why to do an analysis if at all you are confused with the title :).

I wanted to post this after a discussion with one of my friend regarding bug analysis method followed in his organization.

Let me start it straight..

Kaizen is a Japanese term which means continuous improvements, In this method various techniques are followed like Pareto diagram , fish bone diagram , why why analysis etc.., These techniques help us in narrowing down to the root cause of the issue and find a permanent solution for eliminating the cause.

The step by step approach for the above technique is as follows:

Step-1 : List down all the critical issues faced during the project period.

Step-2 : Analyze which issue topped the chart i.e which issue contributed the major percentage.

These two steps are done using the Pareto diagram.

Step-3 : For that particular issue find out the various possible reasons that could have been a cause for the issue and analyze on every reasons.

Step-4 : Narrow down on the cause of the issue.

The above two steps are done using the fish bone diagram.

Step-5 : Now with the analyzed data , gather your team and draw a why why diagram and there you are with your solution.

Step-6 : Find a permanent fail proof solution for the reason found out.

Step-7 : Document your finding and data analyzed.

This method is popular in manufacturing industries. Interesting to know that this method has also been accepted in the software industry.  This analysis is done every month such that there is some continuous improvement in the process and the number of defects also gets reduced, This is a starting phase for zero defect and attaining 6sigma certification.


September 20, 2009 Posted by | Analysis, bug, Process | | Leave a comment

Bug which bugged me !

I faced a really weird situation in  “‘H” ,  never have i come across one like this. I was testing for a login page which had two image ,

1. H image and

2. E image.

I had some interesting plugins in the browser too , (you will know why i mentioned about my plugin as you read on )

when i opened this index page i was able to see both the image , but it so happened that when i refreshed the page , i was suprised to see the E image had dissappered , as a tester i was excited that i found a bug , but wait a min , it happened only in FF and only in my system (Interesting isnt it ? ). We had to release the page after testing in another pc  which did not have any such issues.

The next day , i was testing a bug fix were the level in the UI and drop down should be same. i noticed that when i opened it the level were not changing, the ajax file was not getting called , again i thought, it was bug , BINGO , the same problem. This happened only in firefox and only in my system.

i was thinking for sometime and tried opening in firefox safe mode ( this does not have any plugin in it) , i opened the index page which had both the image and when i refreshed it was fine. and the next issue , it also worked fine. I remembered once reading in my official mail that disable the firebug , it will work fine. i tried the same in my normal FF but it was the same. Then i disabled my plugins and restarted my FF , and SUPRISE eveything was working fine. i wanted to find which plug in made my FF work so stupd and made a fool of me. got to analyse on  that , but as of now have enabled onl my firebug and testing hapilly.

where could the issue be , 1. plug in 2. Browser or 3, Anything else. ???

September 18, 2009 Posted by | bug | | Leave a comment