Solving problems in tester’s way.

January 29th and 30th will be holidays for Moolya testers. Pradeep and Santhosh will be going to Chennai for attending Bug-de-Bug conference and I decided to go home in Pune.

I wanted to book tickets for train and so I went to Jaynagar for the same. I needed more cash for booking so I reach at ATM transaction machine, which supposed to give me cash that I needed.

I found one ATM machine near to the Bus stop; fortunately, it was of same bank, which I have account. After waiting for 15 minutes in long queue, I got my chance for the transaction. I entered the PIN, request for RS 1000. (I need only RS 500 but who knows what will happen and I need more money urgently?). Now here comes a problem. I requested for the money and receipt for the same time, got the receipt for “amount deducted and actual available balance”, but did not have the money.

Oh God, bugs are behind me outside office too! ! !

Here comes a tester’s job now. I got the problem and I want to learn, report and solve it too or help bank people to solve it. My brain started working. (Usually its very slow, but while testing its starts functioning, let it be.)

Now some questions came into my mind as

  • Is it a problem with Machine or me?

(I remembered my steps while doing and I found there wasn’t any unusual thing I did to fall machine in wrong state. I assume now that it is a problem of Machine.)

  • If it is the machine, is it with “hardware” that deposits money or “software”?

(I remember there’s at least four transactions by different people who were successful I guess, and I can conclude that machine at least had not a before my work.  But why? Its so frustrating L)

The machine is in problem now, can be called as in invalid state. This can do more wrong things now if I force her to do particular things. I want to know more that what else it can do unusual?

I waited sometime as might machine is in hang state and will give output after some time. I decided to wait for 2 minutes only as

I do not have much time and chances to do these tasks, as other people are waiting and I know that people can frustrate here if I would take time more than 2 minutes.

Now I have 120 seconds, in that I want to do some follow up so that I would have good evidences to show bank

I already have a one receipt as a proof in which withdrawal, actual and Available balance is showing right but not it did like that. Here some tests I did to achieve my goal.

Next thing I did was To check my balance again. This step is consistent with my goal as if the machine shows right balance I can conclude its problem with hardware or if it doesn’t or shows something improper in receipt, it’s a software or network delay problem.

Why "actual" and "available" in only a balance enquiry?

Actual result I got was In Balance Enquiry receipt it shows two different values for actual and available balance. Expected: There should be only one value to be shown and what the hell is meaning of actual and available balance in Balance Inquiry receipt man?

Okay, I got to know that it’s a software+ network problem too from above, And I have one solid proof with me now to show bank. Now I want to know further

v     If this problem related to my account only or others will also affect by it.?

I told to the guy who is next to me in queue, my problem that I am having here and he agrees to tell me if he also find some unusual thing. (Maybe he will get my money as my money can come with his money if its stuck in the machine.!!!)

He did not find something wrong and went away. Now it’s my time to do one test more (I needed money too,) I request machine (again J) to deposit now RS 1000 and have a receipt with it.

Yippee! Here comes another issue.

See withdrawal amount and deducted amount...

The image here shows that withdrawal amount is 1000 but machine actually deducted 2000 while showing actual and available balance. I got great proof to show the error in machine to the bank.

Feeling happy (I did successful follow up) and sad too (Why the problem is with me?). I decided to go to bank tomorrow morning to report issue.

I wrote a pleasant letter to Manager of the Branch (who knows she might be beautiful), mentioning all the necessary details (unfortunately I can give steps to reproduce the problem) and handed to problem reporting staff.

At last, I ask her a question that is also fundamental in testing

How much time you would take to resolve the issue?”


I appreciate you for the patience you have while reading the post or at least scroll down until here.:)  If you find some learning, its my pleasure, if not, you can mail me  or comment on blog.


Riyaj Shaikh.

WT50 :My Weekend Testing Session Experience

Hi folks,

Happy new year to all. This is my first post in this year.I thank to my small fans for waiting patiently for my new post.  :)

In Last weekend on Saturday 8th Jan, I attended my first weekend testing session.  I was very excited as whole Moolya team is participating in this session!!!! And I decided to write on this.

Here is a summary of things I did in this session.

The session started exactly at 4 PM. Before that  I added weekendtesting on my Skype account . Moderator of session “Ajay Balamurgadas ” asked me “would you like to join?”  I answered yes. He shared me  mission and asked me  if I have any questions?

Mission that he provided to me was as follows

“FireShot is a browser addon which captures, edits, annotates, organizes, exports, uploads and prints screenshots of your web pages.

They are facing a problem with many issues being raised on their support page and most of them lack important information. Please work in pairs and go through the issues logged and add additional information to help the programmer.

You will have to register as a user here:

Can you find the root cause and help the programmer fix the issues faster? Let us see.”

After reading a mission, I was actually stuck for a moment. I was expecting of mission like Finding a bug, or testing or like that. Here I was asked to Find a root cause and help the programmer to fix issues. !!!! Unexpected and nice one.

I took some 15 min. to understand a mission, and registering onto a website. (Only 1 hour provided to complete mission). I needed to do my task in tester’s way. I was on support page to read the bug reports filed by users of this product. I chose problems randomly and try to pick some interesting once.  And decide to reproduce them.

Few of the reports that filed, I found interesting and were really irritating to users of this product as I try to reproduce it.

I said “few” ones before because many reports were not understandable and can to reproducible because of less information that a particular user has not provided (like configuration details). I agreed with JK why was he facing problems to fix those issues , The administrator  of this website .

Also one more thing, the reports were arranged in random sequence. If there is any keyword, priority related to each bug there, it might be helpful to both users and programmers too.

On Reports page there was no option to search for a particular bug. Because after reading some random report s, I wanted view previous last reports. Too bad.

Next, Useful Instructions were not given to Users who raised different issues to provide a screen-shot or video-capture of the problem if they can, I think This will definitely help to programmers to understand the problem, and JK will not comment like this “we can not reproduce this ” of a potential problem.

I found a serious problem like my fire fox browser was hang as I installed this addon on browser and I needed to restart browser again. This was annoying.

We can blame testers of this product for not analyzing these issues before product was launched. This Product feels too buggy. Even the new testers like me, will hate this product as I am getting so much bugs with the product without big efforts.

Pradeep Soundarajan and Santhosh Tuppad did pair testing and come out with report

After the first hour there is discussion between we Weekend testers .The discussion was very interesting than previous session as I had opportunity to discuss with worldwide testers on these issues. This was my first time in Weekend testing so I decide to first observe how they do it. Later, I was also joined in session discussions.

Discussion went for one hour, It given me so many things to learn. (Which?)  I surprised why I didn’t t took part in Weekend testing sessions before. But now onwards I will be. I recommend you to join this sessions- if you haven’t yet. I am in search of someone who can pair with me for next session, this Saturday. Will you join me??

Thanks for reading the post. I will come out more interesting ones, as these days I am learning so many things at Moolya and I would like to share with you too.