A Testers Journey

An ounce of practice is better than tons of theory

Finally a logo for Chennai Weekend Testers

I would like to thank all testers who have joined and contributed to the Chennai Testers User Group. CTUG has been recognized and there some interesting happenings around 🙂

Keep Guessing for that surprise … Will keep you posted on that soon 🙂

Oops.. about the logo.. Have come up with a new logo for Chennai Tester User Group.. This has been designed by my wife 🙂 Thanks to her for such a cool design  🙂

Chennai Testers

And to take part in the testing session mail to chennaitesters@gmail.com

Thanks again to everyone involved directly or indirectly in re-starting the Chennai Testers User Group.

~ Bharath

October 2, 2009 Posted by | Uncategorized | 5 Comments

CTUG Session -1

Date: 27th September 2009
Product Tested: Peazip (Ver – 2.0)

Mission: To find function bugs in the Peazip application.
Tester: Bharath.S
Environment: Windows-XP,SP-3
Applicatin type : Desktop application.

Testing Report:

1. First i started off getting to know about the application as the application was not very intuitive in understanding the functionalities in it. The help file  can be viewed only in the web which required an internet connection. There might be users who would not be able to make use of the help file is they do not have internet connection or if there is some problem with the connection.

2. The application cannot be used only with the keyboard though a few actions could be performed by using the short cuts. The column lines was not visible which had an option of stretching the column size to what ever size the user needs, This feature was not intuitive.

3. When more than one file is selected and right clicked and the option Add to Separate Archive is chosen, For every file a separate archive is opened, the only  way to add multiple file is to drag and drop the file(s) in the peazip which is opened.

4. Select a file in peazip and  click on File -> File Tools – >Erase file This opens up a new window asking to choose a files to be deleted, which is confusing. Users would be performing this action having in mind that the file selected would be deleted.

file erase1 5. When a file in the peazip is selected and right clicked and File Tools -> Erase file option is selected the files gets erased from the peazip and also from the hard disk.

6. Select a file in the peazip and right click and choose File Tools -> Join , This pops up a alert as well inserts a 0(zero)Kb byte file in the hard disk. This behavior of dumping crap files in users hard disk would not be accepted by anyone.join file1

7. When a  file not supported by peazip was uploaded there was an alert which said file type is not supported but can be configured by clicking on the Options tab, But the options tab was not available or i was not able to get the tab.

pwd file not visible

8. Found an interesting bug wherein when a particular type of file was opened the file was not visible in the peazip application but on right click the peazip options were seen and could be performed. Could not investigate more on this issue rite now.




September 27, 2009 Posted by | Uncategorized | 6 Comments

Chennai User group!!

Hi All

Welcome to Chennai Testers User Group. This initiative of mine came from my office colleagues who are successfully managing a Chennai flex user group, immediately i searched for a chennai testing

user group and found one,but wasn’t very happy about it. This led to the starting of Chennai Testers user group, but this group has been idle for quiet some time.

Recently joined the BWT(Banglore weekend Testers) about which i have already blogged. Having had a many interesting and learning sessions my thought and confidence about making the chennai testers user group more active grew. so here i am blogging about the chennai testers user group.

To subscribe to the user group click here

To join in the weekend testing activies email to chennaitesters@gmail.com. Passionate testers in this group will be involved in many interactive testing activities of different kind of


There is also a user group blog which will be worked upon to be more informative.

looking forward for great testing sessions in chennai testers user group.

My Thanks to Ajay , Parimala of Bangalore Weekend Testers (BWT) for their support.




September 27, 2009 Posted by | CTUG, group | | 2 Comments

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

Experience with BWT

Wondering what is BWT , Its Bangalore weekend Testers, Here a group of passionate testers come together and test an application, The testers meet online on Gtalk.  I happened to stumble upon Ajay’s blog and got my self registered to the weekend testing mailer list.

So my first testing session with the BWT team was on

Date: Sunday 13′ September 2009

Time: 5.00 to 7.00

Application Tested : Map section in bing.com

Approach: Systematic Approach

Learning: After the testing session we were discussing the different approach everyone had followed during testing, This was a classic example to prove how testing a same application by different people with different ideologies can be helpful. So a tester should be a person who can think like many testers.

During my discussion time , Ajay asked me  one question, which is, If i would follow the same approach if i had lesser time to test an application ?

I did not answer to Ajay’s question at that time due to various reasons. I would like to answer it now. Here it goes…

My Answer:

According to me systematic approach is best in any situation but it varies in certain situations, i.e..,

If i know the application in and out, Then this approach does not hold good. I would have taken the critical areas and would have tested those areas and if time permits i would have done a exploratory testing of the remaining areas.

If i do not know the functionalities available in the app. i do an exploratory testing to find out the same and then identify the critical scenarios to test it. To perform this task we require time.

So in this situation i preferred testing the functionalities one by one as my target was not to test the application fully but to concentrate on one area and find bugs in that area.

On the whole BWT was fun and lot of learning which is what every professionals require.

to participate in the BWT session send an email to weekendtesting@gmail.com with the subject  BWT <Session Number> Confirmed Participant

September 18, 2009 Posted by | BWT Session | 2 Comments

Knowledge is ocean

This was during my initial days in “H”, To become what we aspire not only requires interest but also hardwork and constant learning. These were the words from Ananth for me to become a quality head / Business Analyst.

1. Programming Concepts:

– Styles
– Syntax Outline
# Code Reading
# Web Application Framwork
– Web Service
– Concepts (MVC , RIA)
– Deployment Structure.
# DB – Design Concepts
# SQL / Query
# Scripting Language
– Python
– Ruby
– Java Script

2. Quality:
# What is TQM.
# Bug prioritisation
# Tools
– Bug Tracker
– Reporting and Assigniong the bug.

3. Project Management / development:
# Agile
# Extreme programming
# Scheduling resources
# Commincation’
# Estimation

4.Functional Testing:
# Involvemnet in design phase.
# Requirement
– gathering
– Analysis
# Test case Scenarios

5. Automation Knowledge:
– Functional Testing tool ( Selenium , QTP ect.. )
– Performance testing tool (Load Runner , Jmeter etc.. )

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


If i don’t write a post about redmine, i am not doing justice to myself, The reason for me saying this you will understand in this post.  When I joined “H” we did not have any issue tracking system nor did we have any project management applications. “A” had asked “M” (An unbelievable developer, i am saying this just by knowing his depth of knowledge:) ) so “M” after his research came up with redmine as a tool which can be used for issue tracking.”M” had done the initial installations and merging with our domain etc… and “K” with tweaking and Db changes.

Let me list down the features that we are using and how we have tweaked redmine to suit our purpose,

1. Projects can be added.

2. Subprojects can be added.

3. Subprojects can be moved across projects and also be made as a main project.

4. logging of issues.

5. Issues can be moved / copied across projects.

6. Issue logging through email.

7. Integrating with our version control (Tortoise SVN in my case).

8. Defining workflow and restricting the use.

9. Defining projects as public and Private.

10. Emailers.

And More….

This implementation has taught me many lessons too . I had suggested to one of the testing consultant and she seemed to like it and here is the link for the credit i got for suggesting redmine.

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

Bug Life Cycle !!

I was browsing through qualitytesting.info when i came across a post where some one had asked if the bug should be closed if the bug is not reproducible. According to me a bug is closed when the issue is fixed and it works fine, Till then a bug is a bug and cannot be closed.
This is a Bug Life Cycle:

1. A tester finds a bug and reports it in the defect tracking system now the status of the issue is NEW.

2. Now the reported issue is assigned to a developer , Now the status changes to ASSIGNED.

3. The developer checks if the assigned issue is reproducible or not. If its not reproducible (Even by the author of the issue) then the bug status is changed to REJECTED or a comment is put in by the developer that the issue is NON-REPRODUCIBLE.

4. If the issue is reproduced then the issue is fixed , now the status is changed to FIXED.

5. The fixed issue is Re-Tested mostly by the author of the issue and if it works fine the status is changed to CLOSED.

6. If the issue exists then the issue is RE_OPENED.

This  is  the bug life cycle.

September 16, 2009 Posted by | Life Cycle | , | 3 Comments