Why the error messages does not stick to their places?

5

Posted by Amit Kulkarni [Admin] | Posted in , , , , , , | Posted on 9/27/2009 03:59:00 PM

I always wonder what all things considered when a application is released for the end users. We all talk much on that all the testers make sure that they check the application from the users perspective but is that true? Or rather is that enough? Do we ever try to come up with something which users will not try but if they what happens.

Over here just would like to share a simple example with your all. I know I am talking with the audience which is much expertised in their domain so this is just me sharing something with you. We all have worked on the paint application from Microsoft - we enjoy using this application. As a kid we love to draw, paint and do funny things using this tool. As an adult we try to use this tool as per our convenience......I believer most of the testers use this tool for taking or saving their screenshots because it is such a simple to use. As an old man I am not sure though - how they are using it but one thing I am sure of that their use is very simple and they do not try go beyond the boundaries. Here is what I tried as an adult as I always love to see ......what happens for a particular scenario which will not considered by users but they at least 1% of them will try this out.

Here we go then. Just follow the simple steps over here....to check out what I am trying to explain. It may or may not be an issue but this scenario should be considered while testing any application.

For basic users: Go to Start -->Programs-->Accessories-->Paint

Experts: Directly type 'mspaint' in 'run' and hit enter key.

Both the things will open MSPAINT for you. Just draw something or type something or use any tools you are familiar with.

Screenshot 1: I just try to draw something as I am not good in drawing. =)





Screenshot 2: Tried to close the file without saving it, so I got a pop-up window asking me "Save changes to untitled?"







Screenshot 3: I just can not think the same unlike others so I try to play with this error or pop-up window. (I know I'm like this only =))







Screenshot 4: The next screenshot will not show the pop-up window because I can move the message anywhere so I moved it out of the window area...to see whether it allow me to do. As a user I thought of the application should not allow me to move the error message here and there......obviously not out of the window area.




The pop-up window or the message is no more accessible to me. I can not get in using my mouse too....because it is just lost somewhere. The only option left to me close the application 'abruptly' and open it again.

I know many of us will argue on this...why would someone like to do this? I tried it then why not others.

I always believe that either the pop-up windows should 'stick' to their respective places like a rock or they can be movable but obviously not out of the focus or window area allotted to it.

I have seen this issue with many of the applications and I always wonder - why? I know this sounds very stupid at the first instant but if by mistake you play with your messages or pop-up window - you not only lose the information but also you have to re-launch the application again.

I got a +ve response whenever I reported such issue and I am here to make the applications user-friendly. So this is all to my fellow testers - consider this scenario too while testing such applications.

Best Regards,

Amit

testing is my passion!!!
http://bugteaser.blogspot.com

Reactions: 

Do you always try to be honest with the application you are testing?

0

Posted by Amit Kulkarni [Admin] | Posted in , , , , , | Posted on 9/25/2009 02:42:00 AM

I do not know how many of us will agree with my opinion. But, this is my opinion and any constructive discussion is welcome.

Do you always try to be honest with your application?

This question struck to my mind...I do not know why but it just happened. Over here I am talking about the application you have tested or testing. As a tester we always cry that we do not have sufficient time to test the application so it may happen that some bugs will not be discovered when you test the application. I believe majority of us will say this - I just want everybody to be honest with this.

I started thinking - why this question came to my mind. I thought to myself.....any reason for this to happen today. I suddenly realize that this is because there was an issue cropped up for the application tested by me some days ago. I just opened the application and try to see what the issue reported by the customer. I said to myself - nice one! I miss out on this one....how? We all know the cost of a defect is more once it cropped up on production site. To be honest with myself...but do we really have bug free application delivered to the production. =) No. So, do I need to feel bad about it that I was unable to catch it? I know for the fact that "obvious" things or "obvious" issues are supposed to caught at any cost because you are following a certain pattern and still you can not catch up then obviously you are not performing the task with utmost concentration. In this case, I felt bad not because it was happened on production but it was not an "obvious" issue.

Bug hunting - it’s a continuous process as we all can not carry out what all actions will be taken by the end-users. We can just assume the scenarios, even if we start to think like an end user still there will be some scenarios which we never try. That’s what happened in my case, the user has tried some actions which were not obvious but then that does not mean that I am not at fault.

This gives me new learning and pump-up for other task in hand.

Best Regards,

Amit

testing is my passion!!!
http://bugteaser.blogspot.com

Reactions: 

A 'Bug' or 'Defect'. Which is more critical?

3

Posted by Amit Kulkarni [Admin] | Posted in , , , , , , , | Posted on 9/24/2009 06:36:00 PM


Just wondering how things work with Bugs and Defects. We know for the fact that these are terms used and they do not have the same meaning. I wonder then who is responsible for a bug and defect. Well, the answer is pretty simple! As a tester your job is to find the bugs - so have you created on your own any. No. You just found the bugs which were there in the application, so the responsibility lies with developer. On the other hand if defect then only the responsibility lies with tester. Am I going away from the basic topic here? 

Both the terms are very well known to testers. These terms appear to be synonyms of each other but they do carry a different meaning - but what would be the IMPACT! 

If you are testing any application and you come across the bugs - you will file them and they will be fixed by developers. This is how the cycle goes on until we have an application which is ready to deploy with zero bugs. Now can we deploy a product with bugs? No. How will you deploy an application when you know it contains bugs? 

With bugs you can not deploy/deliver the product to the customer. You need to make sure that all the bugs which are there get fixed and if any new bugs produced during this activity then fix those too and then you are ready to deliver. The impact of having bugs in the application can halt the delivery of it.

What about defects? Well, these will be found out by the client when the application was deployed or delivered. Defects are found when the application goes live. It can be customer or any user who report the defect and then the customer can question us - how did this happen? In this case, the responsibility lies with tester, as they were unable to catch it in the first instance.

So once we deployed/delivered the application to the customer - if they comes up with any defects then the emphasis on whether to fix them or not. If the customer thinks that these defects will hamper their application at a larger extent then they have all the right to get it fixed. The customer comes with the request to fix them up. Here the "change request" cycles start and we need to fix them.

Best Regards,

Amit

testing is my passion!!!
http://bugteaser.blogspot.com

Reactions: 

Do you fight for your BUG?

2

Posted by Amit Kulkarni [Admin] | Posted in , , , , , , , , | Posted on 9/14/2009 01:07:00 AM

Ah!Not so long back I had logged many issues for an app in the hope that it will for the betterment of the app. As always I worked hard and the app was something special for me so I took more care while testing, also making sure that giving appropriate "Suggestions/Feedback" wherever possible.

After some days the TM started reviewing of the bugs logged by me and my fellow members. The list of was indeed quite a big one so TM has a hard time. The problem was this app was the build was continuously updated for some minor issues and then given to the testing team. On the top of it, as always the release date is close by so we have to make sure that the app that is being shipped of good "Quality" not compromising on anything. Things were going good for me as almost all the BUGs logged by me getting 'Approved' by TM so I had time facing the development team. :) Not really!! We all are friends they were doing their job and I was doing mine.

The very next day once all of us reached to the office - we had a kick-off meeting (aimed at letting us know the current status of the app). Things were going good and that day some of my "Suggestions/Feedback" were kept 'on-hold' saying that it will be implemented in the next release - wherein I do not have any problem with that as I did my job to let them know. Now its their call whether they would like to go for these in this build or will be patched up in the next build. Almost 85% of bugs were already checked by TM and was happy with the work of his team. The same day in the second half I got an email saying that "Bug # was not approved". This is not a new thing but I wanted to know what reason was given to it in order to 'reject' it. I was shocked to see the reason as "computer/system specific issue". I hadn't got panic yet as I know I need to reproduce it and show it to TM on some other system or computer. I did that. The status got changed to 'on-hold' so I was pretty happy that its not rejected yet. This time in order to make it simple, clear and easy to understand, I attached a video clip in order to reproduce the issue - the steps taken by me. This time there was no email but my TM called me up for something. I went to his cabin to what is it? I was about to enter the room but I can still smell it what is it for?

I entered the room and my TM again showed me that he tried many systems and also seen my video clip but still they are unable to reproduce the bug. I asked his permission in order to try my hands on it so that I can show him how to reproduce the bug. To my surprise everything went smoothly and I was unable to reproduce it on his system. I started asking question to myself "Why","What wrong did I do?" I left the room quietly as I have nothing to say more. I continued with my work but still can not get the thing out of mind as in "Why not". All my BUGs are special for me so I make sure that everyone get a due respect. I checked the settings of the app on my system carefully to find out what did I do wrong when I was trying to reproduce the bug. Everything was find and I was again reproduce the bug on my system. I performed the task more than once and all the times I was successful. Later on after numerous tries I found that there is one setting that needs to be checked in order to replicate/reproduce the issue.

I again got up and started moving toward my TM's cabin. I seek permission from him to let me use system again for sometime. He happily handed over the system to me as he was almost done with his list. The first try went smoothly and he put a weird smile on his face. I closed the app and opened it again - I checked the settings to find out that there is a small check box which was not checked - for this scenario if this check box is not checked your app will work smoothly. So, I showed him what needs to be done in order to reproduce the bug. This time again the test did FAIL. I looked at my TM and he was having the same weird smile on his face this. I wondered what has happened but just to memorize that there is a bug that if you change something then you need to save it and re-start the app. (This issue was already being worked upon) I closed the app and opened again and this time the test failed - the issue with a small check box which was not checked so my test was getting PASSED. After showing him how to reproduce the bug my TM agreed and changed the status of bug in our bug reporting tool. The smile was no more there and I seek his permission so that I can go out of the cabin and continue with the work. I got out of his cabin keeping my head a little high on my shoulder as I did not put the weapons down once the bug was rejected but took the control and reproduced it. I went straight to get a cup of COFFEE (I am addicted to COFFEE) and just entered the cubicle where all my team members sits. I just asked them one question "Do you fight for your bug?"

Well, that was in my office and I will not tell you what responses I got from others and all. But, I have only one question for you all who will be reading this blog.

Do you fight for your bug?


Best Regards,

Amit

testing is my passion!!!
http://bugteaser.blogspot.com

Reactions: 

Is comparison - valid while testing new app against the older app?

10

Posted by Amit Kulkarni [Admin] | Posted in , , , , , , | Posted on 9/13/2009 09:51:00 PM

I like to share my thoughts on what I feel. When I interact with my fellow testers and after listening to them after a long discussion.


Today, I just want to discuss on something which I feel needs some serious thoughts. We get a new app to test but we try to compare it with the older app. Is this okay? I am not saying we can not have the comparion but the best approach would be to have the older app as your baseline for new test for your newer app. A tester obviously needs some scenarios, cases, user scenarios and practical approach to the app. But it would be much better if it stays the baseline and we do not get serious with it....we see that the older app has this feature but newer ones does not have one so does it mean that the newer app is not good? So if you start doing comparison you do not get a chance to explore the newer app to its fullest extent.

I as a tester do exploratory testing - and see that some of the newer app does not have the feature which I was using quite frequently in the older app. Does it mean that I should not use the newer app? Not really!! If we start thinking like this then there is no point of having new products in the markets where in the company know that the older app is much robust. But development is all about coming up with new features, attracting to new users and try to get the existing customers/users to use your app which in itself which increases your potential (as a company) in the market. Companies are not wasting their money when they come up with newer app (or rather to be specific new product which have more features than the old ones) os it helps them to gauge what the users are looking out for.

This topic is kind of debate where in I have shared my thoughts on this. Others would have their own say on this which quite justifiable giving their expertise in their respective areas. This blog I just wanted to share my thoughts so I have come up with this. Its always nice to hear from others and their justification for their approaches.

Lets chip in and have your say on this.

Best Regards,

Amit

testing is my passion!!!
http://bugteaser.blogspot.com

Reactions: 

Context Driven Testing (arguably be called agile testing)

6

Posted by Amit Kulkarni [Admin] | Posted in , , , , , , , | Posted on 9/07/2009 12:05:00 AM

I love reading blogs......as I get to learn some good things, at times I get to read a chance of funny story, the way these bloggers are portraying the skills of writing (the most important of all). How do you express yourself?


I have this friend of mine asking me to post something on "Context-Driven Testing" for many days.

So here we go.....

In our day-to-day life....we follow the same procedure while doing so called "TESTING". We have a script ready with us or set of test cases/test suites and we just have to run/execute them all successfully and record the bugs if any.

What do you think - the procedure is more important or the way we test it?

This can be argued by many and I am not here for any argument but would like to second my support to the concept of testing where we do not follow any procedure but would like to see how the software works? These is what Context-Driven testing is all about. You would like to see how it looks or how it works rather than going through a piles of files or documentation.

Context-Driven testing--believes in a way that conforms to the context of the proejct as opposed to the traditional way. Good testing is a part of good testing skills and not any procedure. It just to focus on human context (keeping the end user in mind) than a routine procedure.

There are some things which a "Context-Driven tester" would say on this:
1. What is most important "the end user" or the procedure/tools which we all use?
2. Do you believe in specifications or would like to see or rather directly work on the app?
3. Value added Suggestions/Feedback over the same old routine of completing the testing for sake.
4. We would like to see something new....in a software with more features even if that is out of scope but then 'Why not?'

These people are more passionate, excited, creative and lotz of enthu. They would love to work freely rather than sticking to the same old procedures, plan (which is ofcourse important but can be considered when required) These bunch of people would have so many creative ideas, suggestions which are not mentioned in any document but they can certainly add a value to the app. These people are not sideling the old procedure but they are keeping in mind that things which are going to change in future. These people are ready for any situation with broad and deep awareness of problems in a project with possible testing solutions to these problems.

Some key things about these people:

  • Documentation is not always necessary. Good testers knows how to work with the whatever information they have with them. If required additional information for anything then these people will be very specific about "What they are looking for?"
  • Quality does matter to these people - whether it provides useful and timely information.
  • Not stick to the "Quality Assurance" but believe in testing is providing information to all.
  • No test plan. No test documents. These people do not make excuses of these things.
  • Like an "Advocate" defending the clients case..... these testers will defend the app under test from user's perspective.
Some of the techniques is being used in Context-Driven testing:
  • Exploratory Testing
  • GrayBox Testing
These are mentioned as 'techniques' but more appropriately it would be better to term "CDT" as - What is your approach? Main focus on doing the right thing under whatever things are available to us. More options leads to more new solutions for any situation.

If we all follow the same old procedure then chances are more that -- users will come up with defects in your app. If we start thinking like users, their value added feedbacks then we are going one step ahead of the time -- which will give some breathing space to a user. It is not possible to cover all the scenarios as user might think of but atleast we are trying to cover them.

For more reading you may want to check the following links:
If you have differences of opinion or interpretations with what is stated above then you are most welcome to post your comments.


Best Regards,

Amit

testing is my passion!!
http://bugteaser.blogspot.com

Reactions: 

Your Approach when Testing any app

0

Posted by Amit Kulkarni [Admin] | Posted in , , , , | Posted on 9/06/2009 11:38:00 PM

Well it goes like this.....you are just sitting in the office waiting for the release come to you for testing. :) It does not happen most of the times.....as at times TM in company with PM comes to you and say "Hey buddy!! Why don't you start testing the app while the developers is fixing some minor issues and it will be done soon?"


This question is very tricky and funny too.... :) I knew for the fact that the work is still going on but I have been asked to test the app. Well, if you are at my position....what you would have done? I believe time like these comes in everybody's life...so I am not the only one. The problem with this approach is that ......it is very difficult to make out what it an issue/bug and what not. The developers must be updating files...doing check in/check outs.....so there are so many changes taking place....ultimately results in some "average testing of the app". It does not meant that I am average tester.... :) neither do I am a great tester...but I love my job!

Some things which we can keep in our mind to avoid messy situation for ourselves:
1. check the deadline with your TM ....
2. check the scope of the testing for this particular ver ....
3. go through proper documentation for this release ....
4. try to reproduce the issue more than once ....
5. try to get screenshot/videos for whatever you get .... (without thinking of bug/not a bug)
6. try to focus on "Show Stoppers" which will ultimately gives you some space to breath ....
7. consult senior developers but do not ask them what you see whether that is an issue or not. This is your judgement not theirs ....
8. if you feel that there are too many issues at the start itself..... DO NOT PROCEED!
9. escalate if necessary ....
10. most importantly be focused and calm ....throughout the whole process

This list may vary on your own experiences...... I just shared some of the things which I felt I should shared with you all.

So, do not say NO but have the list ready with you which will force TM/PM to say NO.

Best Regards,

Amit

testing is my passion!!!
http://bugteaser.blogspot.com

Reactions: 

Joan finally agreed its a Bug!!!

1

Posted by Amit Kulkarni [Admin] | Posted in , , , , , , , | Posted on 9/02/2009 05:31:00 PM

We all know that its not that easy what we thing of "bug" may or may not be a bug but if your clients agrees with you then nobody will come in your way.


I was working with this client .....can not disclose the company details but the client name was Joan. He was too specific in his approach that at times it becomes very difficult to convince him. Everytime we get some issue that we think of an issue but Joan (the great) has his own way of convincing others its not a "Bug" but some feature. As a tester we have to be very convincing in order to convince others that ....what we have reported is actually a "Bug". Its an art which gradually ...increases with our experience and the people with whol we are working with.

One fine day I made early to the office and started my work. The release date of the application is getting closer so we have to very careful.....while reporting out issues. I got a hot cuf of "Coffee" for me......in a big mug so that I feel good. I started with my work and making sure that documenting all the things with screenshot for my assist. I find something......so I log the bug in our bug reporting application. As a part of process adherance we have to drop a mail to testing manager and keeping Joan in the loop. As usual I made sure that I backup myself very well (and this time my approach was somewhat different towards the task)...this time... I continued..with my work. The day got over on a good note and I had a different feeling on that day. :) I drop the idea to have another cup of "Coffee" while leaving from the office....but when I got downstairs ....I saw one "tapri chai" shop. I asked my friend to accompany me for this....and we both sat there. My friend can not leave with cigarette so he light one. As usual the conversation started with others over there and with "tapri chai" owner got in. One customer was complaining that the "chai" is not good.....and he will not pay for this. The "tapri chai" owner was very calm, putting smile on face...listening to the customer..... After the customer was done with say...... the "tapri chai" owner said ....... chai to maine khud banai hain lekin roj to tareeka main apnata tha ....aaj thoda alag tareeka apnaya hain ...saheb. Even we had the same tea....but we could not feel the difference.....but after their conversation started I though to myself "It tastes something different" and my friend joined me too in affirmation.

The discussion got serious not...... as you all might be knowing a "tapri chai" in Mumbai can cost you from Rs. 2.50 to Rs. 3.50....... the "tapri chai" owner was trying to convince the customer there is nothing wrong with the tea. Lastly, he said one good thing to the customer....... in your work do you follow the same routine or at times you try to find out some different way of doing the same thing......which may or may not give out fruitful result. If I would have made the same tea everyday.......then also you will say that its the same tea........ and when I tried something else....... to see the response.... you are saying that its not good. Life is not same everyday, our approach can make many things different if we want to. Finally the customer agrees to apy for the chai and left from there.

It struck to me so much so that I asked my friend that we should leave now...as I had some work at home. That day I slept very early....after finishing the work.

The next morning ...again I made very early to the office..... I knew for the fact that I would have got any reply to mail which I dropped yesterday obviously from "Joan". To my surprise the mail subject line says "Good work Amit"........

I opened the mail...and for that issue Joan was convinced with me that its an issue or "Bug". Normally, for all the issues we follow the same old routine....but this time I did some online search, other products, the impact of the bug, why it needs to be fixed. After sometime Joan called me up on phone and appreciated the work.....

As a tester we have to always try to find out some or the other different ways but with the process adherance. These ways not only help you exploring new things but it will definately help you convincing others why the issue needs to be fixed. Sometimes we have to be practical or sometime we have to just one goal in mind to break the application (put as much load as you can), or if you are concentrating on UI then it should look good from user's perspective ...ultimately we are also customers too. If you always follow the same routine then the chances are very less that you will be getting any new issue so always search for some other path.

Joan finally agreed its a Bug!!!

Best Regards,

Amit

testing is mys passion!!!!
http://bugteaser.blogspot.com

Reactions: 
Subscribe to: Posts (Atom)