Thursday, February 18, 2010

Million dollar Issue…………………IS IT SO??????

“Step into an ATM (I think, u know which bank’s) and brush your debit card.Enter a wrong PIN, OOPS! ATM displays the options and allows you to select!!!!!!!!!!!!!!”

ATM doesn’t tell you that “you have entered a wrong PIN” and ultimately when you go on and select any options say for example (Cash Withdrawal/Mini statement), then the system will say “Hey,hold on.. you have entered an incorrect PIN”.

I know,you people will say ”stop this.. we have heard this thousand times before” and I hope almost every tester could have tried this out + commented on the tester who tested it.

Is the above scenario was really a tester’s failure??????? I am sure that, Many will say “YES”.

Reasons could be simple-->
a)you expect the system to say “Entered PIN is incorrect” at the first attempt and also not to take you to the page which has options availed by the bank.

b)Most importantly, some other Bank’s ATM (again u know which bank’s) behaves as per your expectations (ie) it will directly say ”incorrect PIN” at the first attempt and it will not take you to options screen.

I hope, you all will agree with one important fact that “There is NO functional hole” then why nobody(bank) is not showing any concern to correct this simple thing(puzzle remains???).

I will share the explanation(I got/ gathered) and I think, this is my responsibility to break the shackles and say “Hey, its not a tester’s failure” --> i will tell u why?


I have tested(FLASH KACB) a newly introduced card(one of these->ATM/CREDIT/DEBIT) which includes testing of ATM transactions(both Financial/non-financial).

And in due course, I have met the long awaited above discussed issue (???) even though I noticed, I have not taken it as an issue. Surprised!!!!!!!!!!

Yes, that is true but ask me why? because it was according to the requirement and design document!!!!????.

However when I slide over the document(not first time, may be nth time), I was also taken by surprise, as you people and even tempted, by the way the requirement/design documents framed and I decided to dig out the reason.

I got my turn..
An questionnaire session in another module of the card provided me that opportunity to hang my question in front of all business and technical people(who would have involved while framing the documents).

And the answer I got from a gentleman is

“It was Deliberately Done”

Sorry, can you please come again? was my response and he again said ”Deliberately Done”.

Deliberately done---? Below is the explanation which I got/gathered(I think which i will share with u guys).

Technical explanation:

Older Version:

PIN verification will be done twice…!!!!!

Let me explain in two different scenarios.

A-> Enter an incorrect PIN:
When you enter an incorrect PIN, the PIN verification program will be called(First time) and the PIN will be verified. This is the case with ATMs which directly gives you “ INCORRECT PIN” and it will not take you through the bank’s availed options (Remember the sub heading->Old version!!)

B->Enter a valid PIN:
Enter a valid PIN, the verification program will be called (First time) and once the PIN is verified, it will take you to options page(withdrawal, pin change ..etc) and if you select any option say ”withdrawal” then again the PIN verification program will be called (second time), the PIN is validated. Now the system will allow you to do your transaction. However the PIN verification program is called twice.

New Version:

Then what is this new version all about?????

Quite simple…

PIN verification will be done only once.

When you enter a PIN (correct/incorrect), PIN will be saved in a buffer space and then the system throws you the options screen. When you select an option, PIN verification program will be called but only once for validating the entered PIN.
This will avoid the extra call made to the PIN verification program(Cost/Performance) effective.

Business Touch:
An another advantage of this newer version from a business point of view is irrespective of valid/invalid PIN the customer is exposed to the options availed by the bank.(it may sound silly, but it is true- in some regions, ATM is very new and people don’t know what is the use of it).

Extra information: I heard that every bank is opting for the newer version so very soon all ATMs will allow you till options page….even with an incorrect PIN.

Compliment: I take this as an opportunity to thank my friend Sudersan (Developer) who confirmed the above.

One question which I have raised after all above explanation given to me(Untitledtester’s ego?):
Myself: Customer might feel uncomfortable since user doesn’t know what went wrong in his first PIN and not even an instant error message?

Business answer: That will not be an issue because users will not hesitate to re-enter a valid PIN and that will make them fell more secured and the user is exposed to the options availed by the bank this will make the user more familiar to bank And moreover the user is getting the error message with prompt to re-enter the valid PIN.

For instant message:Bank will not give an overlapped screen with options and an error message.

-------------------------------------------------------------------------------------------------

For your information- This is a specific requirement that, to call PIN verification program only once.

My Question to people (only who questions tester's work): If the above mentioned new version is a specific requirement for all banks which has an older version. how can you expect a tester to file it as an issue and take forward????

So how crucial is to know the requirements before testing a live product(which was already tested). Lets unzip that issue, may be in the next screening.(who knows the hidden surprise waiting for you in the very next second?).

Expected version of requirement:
(to be frank the below struck me when I was drafting the above--too late…)
Why can’t we show directly the options, when the card is dipped in and than ask for a PIN when the user selects the option. I hope this will fill all requirements. (I don’t know whether designers will agree because it will be their call).
But I hope someone will give me explanation for this ……………….

Lets Explain,
Venkat
All izz well..




You can catch me@ kpvenkatesan84@gmail.com

Friday, February 12, 2010

MY FIRST BLOG – Reasonable Reasons….

Greetings/Cheers to all.

I am really thrilled to write my first blog and as every other blogger, I am also expecting a very tough journey ahead.

I have already waited for quite some time to kick start the proceedings so let my introduction wait for some time.

HERE WE GO…………………….

This(My blog- UNTITLEDTESTER) is not a reflection of “Everyone is writing why can’t I” and surely not about showcasing my testing abilities(because I am still in initial stage of my testing career - Ocean to drink..)

Then why I have started all this?????

Here are some reasons which you people will expect….

1.To improve my testing skills.

2.To improve my writing skills.

3.To document and to dashboard my learning/gatherings in software testing.

Yes my reasons definitely includes the above but not only them, I will drop out one by one as we move on……

When I decided to write blog on software testing(as far as I know). I have spent almost a day to catch my title (something innovative) but ended as a looser (and I hope many of you think that TITLE doesn’t matter, for them its “UNTITLEDTESTER”).

Oh my goodness, It really takes a lot to write a blog and now I feel the stress/fun that all bloggers will go through and here comes another reason -> WANT TO TASTE how it feels to be a blogger.

Yes I know, tasting a thing is quite easy but taking it regularly needs more dedication and hard work so another reason pops out ->Testing my dedication and hard work….

as a tester’s treat take this blog and test it…

I hope you will welcome me at least to know how long I will survive in this BLOG TEST?(same question raised from me when I thought of doing this).

Some expected results(sorry) comments:

a.V don’t want reasons, V want results..(I heard/overheard u).

b.Write something about testing at least in your next blog (hopefully)..

Eagerly waiting for c,d,e....... from you.

Your positive comments will make be fly and your negative comments will remind me to fly with a parachute. Either way I want you to make me fly…….

Lets fly,
Venkat…
All izz well......
U can catch/chat me @ kpvenkatesan84@gmail.com