Skip to content

Gmail – My thoughts were wrong about it

Many a times, I have heard people talking great things about Gmail. I know that Google has cool products but it doesn’t mean that they might afford to have issues / problems / bugs. Before a year, when I was under training by Pradeep Soundararajan I had found some bugs in Gmail. After finding few I thought I am done with finding bugs. That time I wasn’t aware of Coverage factor which I am aware of now.

Yesterday, I thought of let’s see if my learning has really improved since past 1 year. Last time, I had done testing activity on Gmail registration form. This time also, I wanted to do the same to compare my new skills that I have acquired. I started testing Gmail registration form,

What was my strategy?

– Observation (Observing how the system is reacting and what changes are occurring for each and every input that I am giving)

– Different Input types (I love text fields / input fields)

– Modeling different kinds of end-users

I started documenting whatever tests I was doing and I was taking notes of my observation in Microsoft Word document. I was amazed with the number of issues that I encountered within less span of time. At this point of time, I felt mission plays an important role as you keep concentrating on your mission (Good to set mission before you start your testing activity).

What was my feeling about Gmail after I found few issues?

I personally felt that I used to think Gmail rocks and has been tested properly but, my testing activity on ONLY registration form revealed many issues which I had not thought of. There were many obvious issues. This was a good learning for me not to make an assumption that product is robust before doing testing activity.

Want to know what issues were found?

You might be interested to see set of issues that I found, right? But, currently I am still on the mission and will be releasing my test report as soon as possible. I will update in next upcoming post about my test report.

What will my test report contain?

–          Story on how I proceeded in my testing activity

–          Observations each and every step

–          Issues found (In brief)

What my test report doesn’t contain?

–          No detailed issue reports

–          No Investigation details

–          And many other things that I have not though of


I have been as a software tester for over 5 years. I am a hands-on tester and I've been winning bug battles & testing competitions across the world. I am a testing enthusiast, who conducts free workshops on security testing across India (Covered locations: Bengaluru, Pune, Hyderabad & Chennai. Invite him to come to your location), and monthly meets for testers in Bengaluru. I am also an avid testing blogger.

My interests include traveling, driving my SUV, health & fitness and many others. I mentor budding entrepreneurs, testers, teams in any profession.

Latest posts by SanthoshTuppad (see all)



  1. Mohit Verma wrote:

    Keep rocking man :)

    Wednesday, March 17, 2010 at 12:26 am | Permalink
  2. Very interesting challenge – not because you chose gmail registration page to test but you chose to test your learning’s.

    I will be very interested to read the report.


    Wednesday, March 17, 2010 at 5:51 am | Permalink
  3. SanthoshTuppad wrote:

    Thanks for your comment & I am glad enough to know that you are interested to read the report. I would be publishing it during this weekend *smiles*.

    Wednesday, March 17, 2010 at 10:31 am | Permalink
  4. SanthoshTuppad wrote:

    Thank you for your comment my friend :)

    Wednesday, March 17, 2010 at 11:05 am | Permalink

Post a Comment

Your email is never published nor shared. Required fields are marked *