bugTeaser!!!

A year gone by, a year ahead!! [Happy New Year - 2012]

2012-01-01T00:00:00.000+05:30

With almost approximately one and half hour left when we enter the new year, I just thought of put a closure note for this [2011] year.

This year has gone by, well almost quite a good and a busy one. There were quite a few things that could not be discussed in "public" but my sincere thanks to those who walked with me. For some of the walks, I could not be there with you but I hope you understand it.

Looking forward to this year ahead with the same excitement!!

Happy New Year 2012, folks!!!!!! Enjoy!!!!

Br.,

Amit

Started writing this blog on 12/31/2011 at 10:35 PM IST and completed the blog at 11:12 PM IST

Sunday Jinx with some false claims.

2011-09-04T22:18:00.000+05:30

Few days back I downloaded an app to be very specific a game [Chess game] on my BlackBerry device. The main purpose behind the download to see how many claims made by the game owner are correct, many were correct. Okay, not bad. Let's explore the game a bit now to see few more claims. I visited "puzzle" section where the user can solve the puzzles based on the set condition [if and only if those were fulfilled] then you crack the puzzle, and ultimately declared that you won, I mean you were able to solve the puzzle. So for first few tries I was informed that I have exceeded the number of conditions set, so I need to either try again or quit, the puzzle.

The puzzles were interesting and have set conditions so it is not that easy to actually read what move to make next, it may possible though that even after making correct moves, the app says you have exceeded the *defined* set of conditions, and ultimately leads you to start all over again. I find that part not much convincing, I mean ONLY if I could make the moves which falls under the category [the algorithm] set then only I could be able to crack it, huh? Anyways to continue with the jinx which I set for myself earlier I decided to see how it work out, I mean I am not that bad chess player either, so that should not be much worry. And yes the puzzles have variations too, it means that every time if you make a move and fail, and follow the same set of moves then it may not yield in the same moves by the app, not yours, of course. This leaves the user wondering the app [or the set algorithm] have the luxury to change the moves but the user is expected to expose or rather follow the same set of moves to crack the puzzle, but it turn out other way round, that is later, not now. I was solving the puzzles and now I understand the bit of logic in there so could easily move on to the next one.

Some claims that made me wonder:

User could make two different set of moves and still be declared as winner
User makes correct moves but the app says "FAILED", try again.
User follow the same set of moves after first attempt, but the moves by opponent are different this time
User makes correct moves and there is no way they are not correct, app says it does not follow the defined set conditions

Not to spoil my jinx I noted them down and decided to move ahead, there is no point in stopping by when I can not discuss that in person, with the game owner [developer]. :)

As I move on to next levels the puzzles getting more interested and at the same time, somewhat tough, but I decided I am on for it. Here the *claims* for some of the puzzles made by the app owner didn't justify themselves, and I could see a way to sneak through without even following correct set, or even correct number of steps.

Examples: The app says the puzzle will have 3 moves and then mate, white moves first, which is mine.

So the example looks okay there is no problem with that but I could finish the puzzle in 2 moves but as mentioned it requires 3 moves, right? Then how could I finish off the puzzle in 2 moves, what happen to defined conditions in this case, or am I that smart to complete it in 2 moves. As the app didn't specify clearly or there is this ambiguity that 3 moves != 2 moves, right? Or even you didn't mention that it could be less than 3 moves also, as the message clearly states that I should be taking 3 moves, at least.

3 moves, white makes

If that would have been the case of one puzzle then I would not mind that much, but I could repeat the same fist for others too. By 3 moves it certainly means that if one has follow 3 steps in order to complete the puzzle, and that too, those steps should fall in the defined conditions mentioned internally, that is not known to the user, of course.

Oh! I blocked the clear view of the board for you, I'll get it sorted out that one for you. It would give clear picture to see that one and who knows you may finish off the game in 1 move. :)

Board View - My Moves

I set it up for you too, now it gives clear view for you, I marked the moves that made by me in "red" arrows, so those are ONLY 2 moves, and I am yet to figure out why would I make another move. It is so dead that, and yes by the way the move black makes does matter, but I could always beat this in 2 moves, and yet to figure out where should I go in order to make my 3rd move.

Anyways just to keep the story short I am yet to hear from the owner [developer] of the game, as I reported it via using "Report a problem" link, as I feel, some user may spend that precious time just to figure out where is my 3rd move? Oh, no I could not finish it off in 3 moves, I quit.

Update: Added few more screenshots after I made the moves and in response moves, as it could be seen in both the screenshots that I could complete it in 2 moves. For move details please view the top right hand side of the screenshots. [Update details: 02:10 PM IST]

1st set of Moves

2nd set of Moves

Br.,

Amit

Started writing this blog on 09/04/2011 at 09:30 PM IST and completed the blog at 10:18 PM IST
One update in total on 09/05/2011 - added few more screenshots for more clarity.

A Friday RANT

2011-08-27T16:20:00.018+05:30

The intriguing part of Mobile testing is the more you delve into it the more you enjoy, and find out the ways that could help you shorten the time.

So recently I have added an android device to my kitty so that gives me an experience of comparing how two or more devices will behave for the same application in their own environment. I mean it appears nowadays that if there is website then over the period of time it is get re-written so that it will work with Mobile devices. That is part one. But because there are these OSs that are competing against each other to show that which one is good or bad. That is altogether different topic of discussion.

As a normal user it took time for me too to get adapt with the new device. But it was well worth time spent in understanding the core parts. I was not in hurry at all to get adapted with the new device but it just that a tester in me didn't took that long to adapt.

When I was used to then I decided to have a same application in all the devices that have [I was expecting the app should be available for all of them in their respective markets or so]. It was not that tough part to find out common app that is available for all app, so I found one.

The next step of course to have that installed on all the devices that I have. Some patterns that I observed [starting with installation of the app itself]:

The size of the installer [Does it vary too much?]
The time it took to install [Does it work out more or less same for all?]
The user interaction whilst installation [Does user have much control on this?]
The option presented to the user when installation is completed
And finally, the user is able to run the app

Just curious to see results for some of these questions and I was not surprised much though. Other than the part which I hate most about BB resetting the device. As the app is installed on difference devices so I was expecting a bit of things missing here and there.

The most interesting part to run the app and just work out a bit with them on different devices. I set a time frame to just work on the app for few minutes or so on every device just to figure out how the whole user experience. Not bad when I start off. I was not trying to do any kind of analysis or so, neither I was trying to test the same app on different devices for compatibility as that was not the goal, for this run.

I was more interested in things like:

Transition time [Experience from one device to another, and time to get adapt to]
Interaction with the app on touch screen device, as against to one having physical QWERTY keypad.

It was a bit of RANT that I ran as I just wanted to see how well a user in me get adapted with same app, on different devices.

Br.,

Amit

Started writing this blog on 08/27/2011 at 03:20 PM IST and completed the blog at 04:00 PM IST [scheduled post]

My Guest Blog Post on in-built feature for logs for Mobile Application

2011-08-04T21:39:00.002+05:30

Wrote a guest blog post for Bernard Lelchuk and it went live yesterday on his blog. The details for the blog could find out at : Log @ your help

Br.,

Amit

I don't see any error here.

2011-05-18T17:29:00.000+05:30

Mobile Testing fascinates me and though there is always certain amount of risk involved I like that challenge. Risk in terms of the app that you are testing may cause damage to your device [this statement is not in generic but applicable for few apps]. Having known all these and crashed my device few times I still find it intriguing.

Have you ever wondered whats happening behind the scenes when you use an app on continuous basic? Behind the scenes - I mean which is not flashing on the screen of your mobile but still there is something going on. For some part of your app you may not get an error on the screen and if you don't get it then the assumption of not having any issues comes to the mind, which is the trap though. If you overlooked this then you may be missing the behind the scenes issues. So what to do then?

Make an habit of reviewing the logs frequently. It not only tells you whats happening but there is more to learn from the logs. At the start they may not find that simple to understand that is not a problem so you may want to take help from others [more experienced] to try to understand what it is all about. Over a period of time you try to notice and get a basic feeling about it, if not in detail. That is still quite helpful. If you don't see any exceptions on the screen that does not mean that the app is working fine, but that means you are missing something. Try to find out a pattern from the logs - under what circumstances you get a particular exception, though you may not see any error on the screen. These patterns will help your tests - note them down. Repeat them - review logs. If you are successful in finding that pattern then that boost up your case when you submit an issue for it. Now there will be times when it is hard to find the pattern as it may involve various factors like interacting with other apps, systems.

Though you may find that they provide more of technical information though there is much to learn from the logs. Try to simplify the log details if the information is too much get a copy for yourself. Review it on your system, try to make out from it. Now again repeat the loop of finding out the pattern that may have caused the error. The cycle continues. If you find them to complicate to understand get the help, if not use search engines to see if you get any help over there. I still consider myself as a beginner but I find them [logs] very helpful in providing information. If you find it to complicate then you may want to break down for better understanding.

Though the important thing over here is habit of reviewing them. So if somebody says I don't see any error out here then you know what to do, right?

Br.,

Amit

Started writing this blog on 05/18/2011 at 04:49 PM IST and completed the blog at 05:28 PM IST

Freaking gadgets.....

2011-05-17T15:39:00.000+05:30

I'm sure many people are fascinated with the gadgets they use - and with the technology is moving so fast in mobile industry that it is hard to be left behind. With so many new mobile devices are getting launched or their updated version that makes it even harder to go for the right choice.

Questions like: Should I wait more? Should I give wait for the new launch? Should I just skip this and wait for the upgraded version? The list goes on......

If you're trapped to find out an answer for one of these questions then if you wait more then it will become harder too. The good choice is to see what works for you - what will work for you so that it will not be the case where you buy a device and find yourself all alone. The interesting point though it all comes down to your own choice, but keeping in mind that somewhere down the line you are not left far behind.

The other factor that plays a vital role is loyalty to your old device. :) Well that happens if you're using it for long. I find it very tempting when I look out new gadgets but then I questions myself:

Do I really need this?
Does that suffice my requirement?
Should I wait?
Let me see how the reviews come out and then decide.
Am I become too choosy?
Should I just throw out my old gadgets? [yeah, the one that lasted so long ;)]

I wouldn't wonder if someone has more to add to the list. But if we keep thing pending for long then that even make the choice difficult, as by that time you've few new gadgets in the market. I really find myself in such situation more than often but I opt to take opinions then who have better understanding of the market than me. It really doesn't hurt if you go for that second opinion as that will boost your confidence - next time.

Market research is very vital so as the second opinion as that helps you understand the broader perspective. So much stuff available on the internet [with the help of search engine] the life has become easy but yet tough too. But when you decide be with it so that it will not hurt you.

Br.,

Amit

Started writing this blog on 05/17/2011 at 03:10 PM IST and completed the blog at 03:38 PM IST

Correcting the mistakes...

2011-02-08T17:20:00.001+05:30

Few weeks back I was testing a tiny utility on http://sf.net which I find good for testing plus, I was more interested in using the utility for my own sake. Now that does not mean that I always look out for something that will benefit me but at times, yes!

The tiny utility helps the user in converting the video files in different formats [almost all should I say]. I was enjoying the testing this application not only because I found bugs but because I could see how useful will it be for my own work. I was trying out different formats plus the options available in the utility itself which can be customized by the user. I made sure that I note down everything that will be useful for the developer in order to trace the exact cause for the issue, and in turn fix it. The bugs submitted via the tracker made available so everyone can have a look at them. Because some of the issues resulted in exceptions so I made sure that either I provide the exception log via comments, or upload the log as an attachment to the bug. Pretty good so far!

The next day when I checked my emails there were some emails from the developer of the tiny utility that I was testing, thanking me for testing so far! I said he does not have to thank me rather I should thank him for providing an opportunity for me to test an application. :) The same day I reported few bugs [again some exceptions] for some type of formats.

Where did I go wrong?

Continue from where I left for the day - I continued the testing for the application for various file formats that are available me, or using the converter that is available to convert the files in the format need to be tested for.

This is where things started going wrong - I feel that way though. After getting the confirmation from the developer that they have released a new build - I downloaded it and installed it on my system [removing the old version first]. I reported a bug [an exception] while uploading a file in the first step itself for the tiny utility. I looked at my report again to make sure that I provided everything that would help the developer to understand the issue. This is I believe I overlooked something that should be conveyed though. The file I tried to convert was not just a plane video file, but it was recorded using my BlackBerry device + BBScreenStream [a utility used to capture data from BlackBerry device and view it on PC/Laptop]. I did not pay close attention to this detail though as the format of the file that was saved on my PC/Laptop was .avi. I assumed that it should work without any problem just like other .avi files. But it did not work - and when upload the file to convert it results in an exception. Though I mentioned in bug report that the file I am trying to upload a file which is captured using BlackBerry device and the utility that helps in capturing off the data. I think this is where I made a mistake. I could not share the file or attach it with the bug report because it has some information that is not supposed to be share [confidential stuff]. A few more bugs and I was almost done for the day, as it was too late for me to continue with testing the application.

What did I do to follow-up with the developer?

The next day I see that the developer has closed the bug stating that it could not be reproduced. Okay, I said it to me. They could not reproduce it. Should I try once more whether I can reproduce it? Why not? I again followed the steps laid out and upload the file to convert but it failed. This is certainly not an environmental issue - I looked at the report again and everything looked fine to me. I open the tracker to see what action I can take, or is there a way for me to inform the developer that I can reproduce the issue every time I try. I then decided to message the developer via sf's messaging system. Instantly, I got a reply back from the developer that was quite funny - that I do not have BlackBerry device. :)

Okay, I laughed at the response and again got another message informing that they opened the issue again. That means that gives me an opportunity this time to provide more details which I believe could be useful in this case [I said so because it was not just a plane .avi file]. This is got to do with the output file that is generating by using BlackBerry device + BBScreenStream. If there is something wrong with the output codec and that can give them a clue or so. This time I again updated the bug report by mentioning the name of the utility I used to capture the data from BlackBerry device. [I should have done that earlier may be].

The experience taught me few things that it would be useful for a tester to look at the bug from every possible angle, and making sure that conveying the same via the bug report. Not sure if that would have helped them if I had provided the utility name earlier but at least that would have given them an opportunity to look at the output generated.

Your bug report is your representative. [Lesson from "Lesson Learned in Software Testing"]

You might wonder what happened to the issue though! Well, the issue is still open and I am not sure if the developer was able to trace out the cause for the issue and never asked for it. I wanted to make sure that I inform the developer of the program about the issue and the risk involved but the liability to fix it or not totally lies with them.

Br.,

Amit

Started writing this blog on 02/8/2011 at 04:50 PM IST and completed the blog at 05:20 PM IST

Lesson learned series #2

2011-01-19T20:26:00.004+05:30

What is ignorance? Wiki says - Ignorance is a state of being uninformed (lack of knowledge). Now I will not buy that definition necessarily for my context, but that is not the subject of this post though. Because sometimes we know the risk associated with something but we still go ahead!

We are too closely related with our laptops, mobile handsets and other accessories that helps us in getting connecting with all these. As we move onto a world where we would like to do things on the go and for that matter we have started using our mobile handsets for everything we do. We would like be in touch with friends, surf on the go, check out important widget that helps you arranging the things properly on your device, and we are always in the search of FREE applications for that matter. If you are one of those who is having a mobile handset with active internet connection then I am sure you must be browsing the appropriate folder on your device for any FREE application available for you or not. Sounds good! Even I can not resist myself from checking out stuff that helps me using the FREE applications that does not me anything but works for me.

How do you really trust whether an application you are downloading will not harm your mobile handset? Do you like to try out these application to see whether they fit your requirements or not? Or even do you just try them to see if they works as expected? Many questions and I am sure there will be many answers too. We fail to realize the risk associated with these FREE applications or for that matter even PAID ones. Does that mean we should really stop the usage of these applications? Ah! Not so. If that is the case then we might end up loosing out quite good applications in the Mob World. But you have to be a bit cautious!

Whenever you feel that the application you just checked worth downloading then make sure that you check the reviews, if possible use Google for any information available for the application or not. This information does help you saving from something big as this - see below.

And most importantly backed up your data on regular basis - this does help a lot to avoid situations like one that mentioned above.

Best Regards,

Amit

Started writing this blog on 01/19/2011 at 07:50 PM IST and completed the blog at 08:26 PM IST

50th Weekend Testing Session...

2011-01-08T19:49:00.003+05:30

It is always good to see things with you are attached grow immensely. It gives pleasure when you see the growth in front of you, whether you are a directly attached to it or not. WeekendTesting is ONE such that has spread and grown over the period of time. The credit lies with the people who started the initiative, the contributors for their feedback, and of course the vast majority of testers who made it that large.

The day I see that this will be a 50th Weekend Testing session, I decided to myself that I am going to join it, even if I will be a part of for few minutes/hours. I have been to such session when the number was still a single digit number. From there it has vastly improvised, spread the spark across other territories and the work is not done yet, it will still go on. It has helped many people in a way to enjoy these sessions, learn from them, share their ideas, and of course beware of the traps! :) I don't remember exactly how many sessions I have attended or been a part of it, what I remember is I had a great time every time and I learned something new each time.

Now, here I am not going in the details of the session/mission as that information can be find out at the site itself. During the session one interesting thing was mentioned by Erkan Yilmaz about is it possible to see what worked/what not worked/and of course the point that can still be improved [in short the brief overview of the journey so far for Weekend Testing]. I liked the idea very much but it is hard though to look way back and see where we are standing now! If Weekend Testing can really sum up the idea or provide the summarized version through their site, it would be really an insightful. Keep in mind that it requires lots of efforts though!

On a closure note it was again reviving moment for me to interact with so many testers/listen to them/share ideas/discuss and at times argue [not really]. I had a great time attending the session, sorry 50th Weekend Testing session. :) I know there is still long way to go and I will try my best to be part of these sessions on regular basis but then you don't have to ask for permission when you are a part of the family, do you?

Now I am waiting for another milestone, well not really, as that is bound to happen!

Best Regards,

Amit

Started writing this blog on 01/08/2011 at 07:25 PM IST and completed the blog at 07:49 PM IST

Expecting the unexpected!!!

2010-12-26T01:03:00.001+05:30

How is it difficult to be ready for the unexpected situations? Is it so difficult to expect the unexpected during festive seasons? Well, the answer may not be a direct one.

Three days back [to be very specific on 12-22-2010] there was a issue with Skype. There were issue with the "supernodes" and that affected many people around the world. The information on this issue can be found out here, here and the latest update over here. With the promises from the companies on rectifying the issue and resolving on the priority basis, what is the chance that it will not occur again? Zero? Really? Or it depends?

Today, it was twitter as it was down for a while. The update on this can be found out over here. The impact of this really annoying to the users when they just would like to wish the world "Merry Christmas!!". :)

So, ultimately when there is any hotfix made - what are the chances that we will not face such an issue again? Is it possible to expect the unexpected?

Merry Christmas one and ALL!!!!! :)

Best Regards,

Amit

Started writing this blog on 26/12/2010 at 12:20 AM IST and completed the blog at 01:03 AM IST

Twitter services unavailable!

2010-11-01T16:26:00.003+05:30

Should it give me the error message once it log me into Twitter and then says : Twitter services are currently unavailable?

If the services are not available then do not log me in and inform me! By logging me in you're asking me to wait for the tweets to load before you show them all. I would appreciate if you could just **skip** that process if the services are down. It would save a lot of time!

Best Regards,

Amit

Started writing this blog on 11/01/2010 at 4:20 PM IST and completed the blog at 4:25 PM IST

-Conversion error-

2010-10-23T14:00:00.001+05:30


-Conversion error-

On my Nokia E63 I was just checking the emails and it worked all fine until I reach to this particular message. Now let me tell you that this is not an ordinary email with ONLY text but its a newsletter with lots of links, images etc. I tried to find out the cause as why am I getting this error but could not reach to any conclusion. I have already put this on a reminder list so the next time I will get the newsletter - I will be checking it to find whether I get the same error.

Best Regards,

Amit

Started writing this blog on 10/23/2010 at 1:45 PM IST and completed the blog at 2:00 PM IST

Lesson learned series #1

2010-09-26T18:10:00.002+05:30

It is my passion to get my hands on the gadgets and try to explore them. Obviously, I will not ask friends, or relatives to lend their gadgets to me as if something goes wrong it will be me the culprit. I was scold by my father in my childhood for using my uncle's gadget and something went wrong with it [it was a lesson for me]. Since that day it was his teaching that kept me out of these possibilities. I do not have any regret for this and I happily appreciate the advice that he gave me in those earlier days of my life.

However, I enjoy the exploration on my smartphone and practice various testing activities. It took a while to understand everything but it was not that much time though. It is always fun when you explore on your own rather than following some set of well outlined instructions. This way you get to hit the spots where the outlined instructions might not want you to go [for good or bad reason]. It is just like not to follow the scripts but to use exploration, and learn more about the product. [What the instructions would not have taught me, if I have followed them?] Things are really fast when something has to be checked and the mobile plays a vital role. It may take time to put on your system, connect to the internet but by that time if you have access to internet on mobile, you're almost done. There is indeed wide range of things that can be checked on a go.

Mobile testing is an area where you need to have access to various devices as that gives you clear idea of a problem you might come across. It is also important as it helps in broader coverage for testing of the application. Having few devices with me it is at times becomes difficult but then I try to spend some time on investigation on web whether this is a problem with the set or not. Different devices have different capabilities when it comes to the support for features. So, in my case having access to the smart phone that I have, I need to try out various options, ways to conclude that I have come across a bug.

Simulators or the testing for mobile sites on web does not give the real, accurate information, and at times it performs totally different for various reasons. It is always good to test something that is supposed to test on real devices and these option can be tried out to double check. The decision is very important when you come across some problem on your device, this may cause for various reasons connectivity, features not supported on the device, there is some problem with the application you are testing currently. The best way to tackle this problem though to make use of available resources like take the screen shot of the problem or try to make a video. Once you have this information then you can again try out the same set of steps to make sure that there is indeed a problem, and if you do not figure or do not come across the problem again, that does not mean that there is no problem though. Here the earlier videos or screen shots you have plays the vital role and you can search for the problem on the web to see what all results it displays. If you see the problem you come across has been reported then there is indeed a problem but now you need to make sure that you have to reproduce it. Patience is the key.

Best Regards,

Amit

Started writing this blog at 5:45 PM IST and completed the blog at 6:08 PM IST

Testers do not assure the quality.

2010-06-24T14:12:00.005+05:30

For the past few days I was excited that I will be getting a chance to be a part of the webinar by Michael Bolton on Testers: Get out of the QA Business organized by EuroSTAR conferences.

Well it did not go that well at least for me but I figured out the problem occurred in the initial stages due to some technical glitch. By that time I got a chance to get in it was almost all over but that did gave me hope that I am up for something BIG but not this time though! :)

I got in touch with contact from EuroSTAR to see if they have the recorded version of it but got a reply that their recording mechanism also failed when the Live Meeting went down. However, the good part was they shared the slides available at http://www.eurostarconferences.com.

Thanks Michael for sharing the slides here and here! :)

Must read to understand the bigger picture:
Testers: Get Out of the Quality Assurance Business
Doing Development Work vs. Doing Quality Assurance

Best Regards,

Amit

testing is my passion!!!

Started writing this blog at 1:58 PM IST and completed the blog at 2:08 PM IST

Communication: A bridge or barrier?

2010-04-09T16:54:00.006+05:30

It is very important how you convey the message. It all depends on whom you are trying to interact with – management, analyst, programmers, and testers or directly with the client. This information is indeed a very important piece but the most important thing is how well you convey this!

Testers need to have good communication skills so that it will be easy for them to convey the right message. We (testers) have to have good communication skills for various reasons as it helps in preparing bug reports, meetings with peers, and any updates for the clients. May more!!!!

Communication can be a bridge or a barrier. Why? It all depends on how you look at it. If you are not good in communicating things – what problems do you face? There are various different types or even more different things you have to do in order to get the message conveyed.

A bridge:

If you are good at communicating then it will be easy for you to explain the issues, write well written bug report (from the vocabulary point of view), meetings with peers, clients etc. There are other things that make it easy but if you clear this hurdle – it does make sense.

If well communicated then it is very unlikely that there is any chance of any misunderstandings for developers or even for the clients. There will be no need for a developer to call their fellow colleague and ask them what they mean by this? (Something in their report). Over here communication is indeed act as a bridge, not act but it is a powerful bridge. Those who really work on their reports with backed up with good communication skills certainly have higher chances of making it BIG. That really does not mean that a person who is not good in communication can not be a good tester. They are.

E.g.

These people are not afraid of sharing their ideas with their management – even if they are not directly reporting them.

A barrier:

It all comes when we get a practical experience or exposure to live industries. We can communicate things with our friends, parents but that communication is different than that of communicating with real world, real people – who are listening to you carefully. For most of us this is a barrier on how to talk with these real people who have questions ready for everything you say. No one is perfect – it all takes some efforts to be good at communication but if we try then we can. For those who does not take it that seriously will get success initially but it will be stagnating thing for them – doing the same work, no improvement, no appreciation, no progress.

It becomes a barrier when we fail to convey the message to our intended audience – it can be your colleagues, people in management or in some of the cases clients. We asked questions for everything as why something you just now mentioned is not clear – elaborate. If this becomes habit or a thing happens quite often then it is a barrier. The problem is they somehow not confident about their testing skills if they lack in communicating the things well.

E.g.

A good tester who feels communication as a barrier for them thinks 10 times before they approaching their Product Head with the brilliant idea they have in mind.

A workshop or internal training is being conducted but they are afraid to ask questions because they feel it is a barrier for you.

When the shuffle happens and someone moves from the category of communication as a barrier and now a bridge that is when a real change in their lives.

Best Regards,

Amit

testing is my passion!!!

Started writing this blog at 4:00 PM IST and completed the blog at 4:50 PM IST

Resolved. Please check the note.

2010-03-30T18:25:00.003+05:30

In my last assignment I had to use the clients bug tracking application. It is good to have a tool than to have separate documents prepared by the testers and share them with developers. It helped me a lot in order to prioritize the bugs accordingly and that helped the development team to fix them. The assignment was about to be over and I sent a reminder mail to see the status of the bugs, although I can see them using their application but it was just my way of reminding the development team. Although there was no update from development team but I got to see a status update mail by PM – fair enough!

It was the next week (last week) for the assignment from my side – I saw some updates from development team as they were busy with some enhancement.

Some questions to my mind:

What is more important? Fixing current issues or working on enhancement?
Why not fix the issues which are of high priority?

Well as they say testers job is to raise the bugs – it is stakeholders, client, PM responsible to answer all these questions. Move on.

One fine day flooded with emails on notifying me to verify some of the fixed bugs. I was happy to see that some of the have been fixed and some of them have been just marked as fixed with a note:

It is not harmful. (Me: Harmful???)

It will happen if the user intentionally tries that. (Me: that. What is that?)

Okay so I understood one thin that even the development team is not aware of how to use this bug tracking tool? Hmmm. After watching some of the notes the development team has entered for some of the bugs I was sure enough either they don’t want to fix the issues, or they are over-loaded with the work in their hands.

Some more questions:

Does it happen that when the deadline for the application come close, the development team starts closing some of the issues?
Why not ask for more details from testers before putting such a note which indeed does not convey any message?

As a part of assignment or my working style – I had conversation with PM and informed them about this. Even I tried to pull a chair for my colleague developer to inform them on not put such notes as they really do not serve any purpose. Nod from a developer. (I do not know if that is “Yes” or “No”)

Final day of the assignment and I was working on the email to keep informed all on the status of the issues logged during the iteration. It was indeed a mixed experience during that iteration and I just wanted to help the team improve on the quality.

Now it is been 1 month that my assignment got over and I just wanted to see what is the status for those bugs – where the development team has put such notes. Just out of curiosity. :)

It was indeed altogether different experience as I saw some of them now have notes from the person who was leading it. They made it clear not to put such notes as they do not make sense to management and also put their own notes – of course by changing the status too. (More work for development team, it could have been avoided at the very first instance)

So I close this post by asking you a question.

Have you come across any note which does not convey any message?

Best Regards,

Amit

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

Started writing the blog at 05:25PM and completed the blog: 06:15 PM

An apology to all!

2010-03-09T00:36:00.000+05:30

Hi All,

This is my sincere 'apology' to all as I could not live up to the task of writing my thoughts in a form of a blog. Its been a three months now the last time I added new entry. There is no lame excuse for this and I don't want to give any.

I have decided to move ahead rather and take this as a learning curve. This 'apology' is to all (my friends, my mentors, my testing gurus, and to the testing community) even though you have not visited this blog anytime but my apologies to you too!

I hope to move on with this on a positive note and I hope you all will help me out with it!

Thanks.

Best Regards,

Amit

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

Importance of being original!

2009-12-23T17:59:00.001+05:30

A healthy and upfront conversation can easily resolve any kind of misunderstanding. This blog has nothing to do with testing but then, it has something to do with testers nonetheless.

Pradeep Soundarajan a friend of mine remember me after a long time. The conversation started by greeting each other and I was pretty happy to hear from him after a long time. The expression on my face from being happy to being "confused" changed so speedily, that even I just chucked my nails. Pradeep shared one URL with me and with excitement I opened the URL to see what in there! To my surprise the URL has a blank blog post with my information and it was having the words from Pradeep's blog "Tester Tested". He was calm, polite throughout the conversation and mentioned that he just wanted me to have "originality". How true is that? I'm follower of his blog post and never intended to do something wrong or try to use them for my sake. The question others might ask them - how did this happen?

The story behind the blank blog post goes like this - the first time I started blogging I was just wondering why not to write about "Banglore Weekend Testers" (BWT) and now known as "Weekend Testers" (WT). To make things worse I had read one post from Pradeep's blog so thought its his idea. I created the blog post with the name "Tester Tested" as I thought this is how you've to do? First time blogging though! But did changed my mind and created another blog instead. However, all these days the other blog post with the name "Tester Tested" has nothing in it just there in "Hide" mode. After that I used to post my blogs in other blog which is under the head "bugTeaser". So this is how this all happened.

Moving onto the conversation, he explained me, I'm being "original" in my thoughts that will naturally come through my blogs post then. I quickly figured out the issue and deleted the blank post with the name "Tester Tester" which was lying there all these days. Being a very formal person, I did "apologize" to him for all this mess up. As a good friend and a good human being, he understood the mistake but asked me for a promise to have a cup of "coffee" with him when we meet.

This blog post is just a conversation between two friends - the misunderstanding and the quick fix.

Best Regards,

Amit

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

Started writing the blog at 05:25PM and completed the blog: 05:59 PM

Keep the error message SIMPLE.

2009-12-17T02:12:00.005+05:30

Its all about how to keep things simple for any application, that way it can make more sense to the end user. I do test applications on my own, and at times if I've to register on any site I've follow the instructions given. How many times you've seen error messages which are not understood by the user? I'm the user too!

It is all about keeping up the things simple for better understanding. There are people who do not know what is "server", "administrator", "null" etc and if you use these terms, you're just confusing them. There are no rules for any error messages as it is been decided by the company who introduce them in the market. They all can not work on the same page but they can follow the simple thing which is - keep things SIMPLE. If a user do not understand anything from the error message, then they are not sure of the next step they've to take. This can have direct impact on the business like dis-satisfaction, loosing users, chaos all around. As a user I do not know anything about the application, which can be learn and understand by using it. The more I use it, the more I understand it. If my first experience with any application does not give me satisfaction which is directly

related to my "trust" in the application.

Thumb Rule: Simple things are easy to UNDERSTAND.

Some of the things which can be SIMPLE from end users perspective:
1. Error messages should be understandable.
2. Messages in English helps user to make out their way.
3. Using word like "null", "exception", "misconfiguration" does confuse the users, they are not aware of this terminology.
4. More information is available in the server log. Confused User: What is server log?Where is it? How to get? What to do with it?
5. Avoid questions and provide answers straight away (instructions) that leads to solve the problem.

KEEP THE ERROR MESSAGES SIMPLE.

Best Regards,

Amit

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

Started writing the blog: 1:45 AM and completed the blog: 2:12 AM

Can you fix that issue now? :-)

2009-12-04T21:59:00.006+05:30

How many times this happens with us (testers)? The issues reported by you - get rejected or closed saying that the user will not try such weird thing. I believe this is a part of every testers' life. Correct me if I'm wrong!

This story happened quite a time back, not so long though. I reported one issue - reported and assigned the issue to the developer working on that project. As per the practice sent out email too to make sure that everyones is aware of it. Few days passed by like this as there were some other issues too. I'm being assigned back the issues fixed by the developer, so I had to perform regression testing. One morning I just came to the office - such a fine day (because it was Friday) so I was more happy. :-) I checked my mail and surprised to see that the developer has re-assigned the issue to me the one reported earlier. The developer asked me to close the issue - Reason: "User will not try such a scenario, so can you please close this issue. Thanks". I thought I should talk to the developer for the last time to make sure that - this is what it meant. I went to him and queried about it and found that he meant the same. After discussing the same with TM,PM and concerned developer - I decided to close the issue.

Months passed by and the project was successfully deployed. Everyones' happy. ;-)

Everyone busy in their work and just working on the other project. The one fine day we got an email which was forwarded to us by our PM - says that the issue # xxxx need to be fixed on PRIORITY. Meeting has been called for the same by PM. We went to the meeting rooms (not to mention carrying out pad/pen with us) and found out that the discussion was getting heat up. After a good analysis in our Bug Tracking tool we found that I closed the issue but not to mention that, notes section contains the reason the developer has given to me. They questioned me and I answered back that this is the same issue that I closed for the reason given by developer. I was safe as all the time everyone aware of this. Then PM started saying that one user has indeed tried the scenario mentioned by me in my report and there is an issue now. This is the users' response and now the customer has asked us to FIX it. Meeting ended with discussing the things like fixing of the issue on PRIORITY, time spent, time for testing, what needs to be done on PROD and analysis report which needs to be submitted by TM.

After coming from the meeting room I went to developers' desk [not to mention big smile on my face :-)]....just asked him:

Can you please fix the issue now? :-))

Best Regards,

Amit

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

Started writing the blog: 9:20 PM and completed the blog: 09:59 PM

CAPTCHA! Why you're not in CAPS?

2009-12-03T00:40:00.000+05:30

We always talk of making life simple for end-users and so we "testers" come up with good suggestions that will really make is simple. Good job guys! Really?

By the way - What is CAPTCHA? Completely Automated Public Turing test to tell Computers and Humans Apart. A CAPTCHA or Captcha is a type of challenge-response test used in computing to ensure that the response is not generated by a computer. A common type of CAPTCHA requires that the user type letters or digits from a distorted image that appears on the screen. E.g. post available for public, registration forms etc.

I have filled up so many registration forms, blog post where they ask for CAPTCHA to be entered by the user. But I always wonder if the application has kept the CAPTCHA in UPPERCASE letters that means if all the combination of letters and numbers, if they are in UPPERCASE letters then why not automatically enable CAPS lock on when the user move their focus to this field. Any security issue?? Nah...I don't think so.

So many sites I've seen with CAPTCHA in UPPERCASE letters but when the user move their focus to CAPTCHA field where the user has to enter the letters, they first have to put on CAPS lock ON. Isn't that pain for the user? IMO.

Why it is not possible that when the user move their cursor to CAPTCHA field, automatically their CAPS is lock is ON or if not that, then while the user enter the characters as per the CAPTCHA image - it should display in CAPS. What it does?

The user don't have to perform one more task of putting on their CAPS lock ON again!
The frown on the users face if they fail to put on CAPS lock on and enter the character and hit "Submit" button.

I believe that for any application (site, blog etc.) if CAPTCHA is going to be in UPPERCASE letters then make sure that, the application will either display the characters in CAPS or it automatically enable CAPS lock for them!

How it would be? When the user reach to the text box as given in below image - the application is smart enough and turn on CAPS lock for the user OR it display the characters in CAPS which the user is entering but they have not put on the CAPS lock.

Isn't that useful for the user?

As always I wonder - if what I assumed is not a good OPTION. What say?

Best Regards,

Amit

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

I'm not responsible for that.

2009-12-02T01:50:00.000+05:30

How many times we've heard that testers are not ready to accept their mistakes. It is common scenario but rather unusual though!

We say ourselves as "Quality" masters but then we fail to face the truth. There is nothing wrong in accepting the truth and move on, and also make sure that we learn from these mistakes though!

I was just watching a team where developers and testers were fighting on the issue that cropped up and now there is stakeholder for it. This is not a true team work then. There was one issue cropped up on PRODUCTION and frankly speaking the testing team should have taken the responsibility, but no they're just shouting out We're not responsible for that.

When you succeed you make sure that all credit goes to you but when something goes wrong, there is no one to accept the responsibility. I term this as "ownership". This is applicable for all the teams and the task in their hand. When you take ownership for any task then it is your responsibility if anything goes wrong then you'll be held responsible, and if everything goes smooth you'll get all kudos!!!

We're human being and prone to make mistakes. The best way is to learn from these mistakes and try to make sure that we'll not repeat them! Rather I'd say its always better to make mistakes so you know the importance of them and the lesson you learn from them.

The next time you make a mistake, accept it and learn from it.

Please do not say I'm not responsible for that.

Best Regards,

Amit

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

Do you still stick to best practices as an "Expert"?

2009-12-01T01:16:00.000+05:30

Every company or organization have their best practices in place in order to run the operations smoothly. As the company or organization increase its become hard for Management to keep an eye on all the "Employees" whether they're following the best practices. You best practices include the work process, the escalations (if any), the efforts by teams and many more.

If you're novice to a company or organization then it takes time for you to get in the comfort zone. This is a scenario which mostly observed and there is nothing wrong with it. It is advised to a novice tester to seek or rather gain experience on their own, as that will help them to become an expert one day. There are some tricks and tweaks which they have to learn as the time pass by. I'm not saying please do not stick or adhere best practices of your company but try to find a better way for you. It is always advisable to cultivate own ideas which are within the limits of your company or organization, but at the same time are quite handful.

However, the problem starts cropping here. A novice user who got good experience now moves to state where they just makes sure that, they have to secure the job. Such resources are good in their given work but then there is no returns from them to the company or organization. Every company or organization would like to see their employees come up with new ideas which they can include in their best practices. This is the responsibility of an expert user to try and make sure that they try to find out ways of doing the same things. Best practices are for betterment of the employees as well as company or organization. This hurts when a novice employee come up with an idea and discusses with it an expert, but they do not see any or rather get any response from them. This demoralize the whole purpose of innovating new things of doing the same old tasks. This is bad both for the employee and for the company or organization.

"An airplane pilot doesn't refer to a manual". Likewise, the experts on a test team should not be required to go by the book which are the best practices referred by your company or organization. Best practices can be a birth of creative ideas, innovative ways of doing the same old things but in new way. Even if the expert employee is ready to take an initiative but because of the best practices levied by the company or organization can become frustrating at times. The Management has to make sure that they listen to the new ideas, innovative ways of doing things and encourage the employees.

The best way of doing things is not just following best practices levied onto the employees but make amendments too.

Best Regards,

Amit

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

Can you test the application completely?

2009-11-27T00:30:00.000+05:30

I know guys this is been after a long time I am again writing a blog. Not so long though! =)

There is been so much said about testing but it is always learning - and I'm still learning. There is a long way to go.

I was working on a project for a past month and the work is not completed from my side. The day I finished the work my client asked me - Is testing completed? I answered them back in affirmative - as I interpret the question as they meant to ask me whether I've finished my work. They laughed at me and re-phrase the question - Have you tested the application completely?

I said to myself ....huh!!!! What I interpreted was totally different from the re-phrased question they asked me.

I tried to explain them it is not possible for tester to completely test the application. Even if they spend all their life there will be some scenarios that they might miss out. As a tester it is not possible for you try out all the possible permutations/combinations as there are so many. We can decide a phase in testing cycle where we can say that the application can now be deployed. The client decides when to stop as the costing is their territory and that is not a thing that a tester has to worry about. The look on my client seems to be satisfactory so I said to myself time to move on.

I thought of this question so many times and it is just not possible to cover all the scenarios wherein you can say that this application is bug free. A user and tester have altogether different mindset so their approach towards using the application is obviously different. A tester can think more or less like an end user but vice-versa is not possible.IMO.

In a testing life cycle there are so many iterations takes place and even after completing all these iterations can you say that you have completely tested the application? Can you?

Best Regards,

Amit

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

I speak for the user.

2009-11-14T19:06:00.000+05:30

A tester's job is makes sure that the application they are testing is working fine under the normal scenarios. How many times we've seen testers and developers arguing on an issue where in tester is saying that it is a bug and developer is saying it is not! The argument continues.......

I speak for the user - this is the most common reason from any tester when any argument takes place. It is feasible as long as a tester is fighting for the most obvious issues, but how about the scenarios which a user may not even try. Developers do not have any problem fixing obvious issues, but what about the scenarios which the tester tries which a user may not even try in their life. How many times in a meeting for project a tester says that the user hates such issues and I am speaking on behalf of them. The next question someone may ask - whether the user has appointed you as their agent?

If you always come up with this excuse for your issue that the user will hate it then obviously that makes the developers unhappy. Testers work differently than that of the users as they want to make sure that application works fine for all the cases. But then is it fair? I have seen, heard or been a part of meeting where such argument takes place. You assume that the scenario you have tried will be tried by the user and if it is not fixed that will be a loss. Is that so? Think again.

As a tester we need to change the most common sentence while justifying any issue – “I speak for the user.”

Best Regards,

Amit

testing is my passion!!!!

http://bugteaser.blogspot.com

Halloween Scary tale!

2009-11-01T21:59:00.000+05:30

For the first time the situation is so bad. The latest one is that bugs are stalking programmers/developers like anything. Always the scenario known that programmers/developers will not see bugs from naked eyes, even if a bug says I'm here they will ignore.

This Halloween though - all the bugs got together and the leader of their union stands in front of all these bugs for a speech. It all started with distributing in different groups - the task given obviously stalks the developers/programmers. The groups were allotted different parts of the world and they have been starting the mission as soon as possible. Every bug listens to their leader carefully and raised their hands for questions. The mission notes successfully noted down by the group leaders and started with the journey.

The mission - stalk the developers/programmers. Just stalk!!!!!

Every one of the group leader then informed their team on how they will complete this mission. The masks were distributed by the group leaders to the team members. Each one of them put on the mask and shown it to the fellow team members. Mission started guys!!!!!

Developers/programmers all across the world enjoying their Friday fun and unaware of this. One developer who was online tweet one of his friend that they have seen news flashing on LCDs about the mission of bugs. The news spread like anything but that did not demoralize the bugs from the mission they have been asked for. Bug started following stalking developers/programmers and didn't hurt them.

Developer: Why are you stalking us?

One of the bugs: This is our mission for this Halloween.

Developer: Why are not you staling testers as they are the ones who find you?

One of the bugs: They do their job but you don't.

Developer: But I never see you with my naked eyes?

One of the bugs: Tester finds me just like that and you don't, why?

Developer: May be next time I will make sure that check everything.

One of the bugs: Every time you say the same thing and newer releases too have the same bugs which are supposed to be fixed earlier and reported by testers - just your note "not reproducible" "deferred" and we still there very much.

Developer: Next time I will sit with tester and learn from them on how to find you. Is that okay for now?

One of the bugs: Just don't sit with anybody try to make sure that you deploy everything with less bugs. =)

Hey where are you going bug? Well the mission is stalk developers/programmers, I guess you learnt your lesson and I want every developer/programmer learn this. So I am going to find the next developer/programmer.

My mission will not end till I teach the same lesson to every developer/programmer.

Best Regards,

Amit

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

The networking is invaluable

2009-10-19T17:24:00.000+05:30

I hope all of us have a good Diwali and I hope all the good things for all. I just can't stay without my laptop as I need it all the time to see what all is happening around me. I'll be discussing one of the most important aspect in real and professional life today.

What do you think of networking?
Importance of Network.

We'll use twitter, Orkut, Facebook etc.....all these networking sites helps you get to close with your friends. My question though: Do you believe you network on whatever site it may be helps you in real and professional life. We use all these for fun or just to be in touch with friends.

For me networking is an important aspect in everyones life as it gives you what all think, what they think, what make them think so etc. In my professional life (testing) this is an important aspect if one wants to keep updated with the latest things happening around them. With my network I can ask their point of view on things which needs constructive discussion and for that I need to have large coverage. My network is not just for fun but it add additional value to it of sharing the knowledge. To keep myself updated I always have so many questions to ask these gurus who can advice or give their opinion. Ultimately its me who is going to decide what is good or bad, but its good to have the opinions of others to make the final decision.

It is an important aspect in everyones life to understand what others think, what they think, what approach they take while thinking, and what makes them so successful. I'm in a phase where I'm just working on my network to grow but I must admit that it has helped me a lot! Even I've big plans - one of them would be to meet-and-greet other testers from other cities and have a casual get together with all these people. I'm just working on how to implement it? This one needs lots of planning, resources etc so I've keep the thing on hold for a while.

I've been observed the trend that if you're active on various platforms, forums, networking sites and make use of them, it helps a lot. Think of a scenario where you can interact with hundreds or thousands of people virtually and get their views. This helps in your real life as well as your professional life. If you follow all the gurus - one thing is common that they're always active and always sharing the immense knowledge they have. To grab this opportunity you just need to follow them and get their views - free of cost with no more time!

For me networking is an important aspect to be always touch with others and enjoy the knowledge sharing process.

Bottom line: The networking is invaluable. What say?

Best Regards,

Amit

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

What do you get going day in day out?

2009-10-07T02:12:00.000+05:30

I read blogs and find some interesting stuff about testing. The question comes to my mind what is that thing which keeps them going on and on. Ah!! Here we go. It will vary as per the person but there are some patterns which I've observed.

Some patterns like:
(a) curiosity
(b) zeal
(c) excitement
(d) innovation
(e) creative ideas
(f) always find out other way to do the same thing
(g) motivating yourself that you're doing wonderful job!
etc....

The list can vary for others as per their priority as I tried to cover the hot ones. People can argue here as to what all things has to with their work. My friend....it will not only gives you new ideas or brainstorming ideas but also you'll find that you've raised the bar in your productivity. It always matter what attitude we keep the work we're doing. If some task comes to your desk and you say it is just one of those which you hate then definitely it will make you feel worse! But what if we try to find the different ways for the routine and add some flavor to it ....wouldn't it be good then?

All gurus of testing always on hunt for innovative ideas on how to do the same work day in day out. It serves two purposes it gives them a good brainstorming and at the same time the joy of doing the task in hand. These people will never complain about the work they're doing. Wouldn't it be great to join them?

I am just in the phase where I'm trying to innovate some ways to complete the task in hand with a big smile on my face. :)

Best Regards,

Amit

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

Why the error messages does not stick to their places?

2009-09-27T15:59:00.000+05:30

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

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

2009-09-25T02:42:00.000+05:30

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

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

2009-09-24T18:36:00.000+05:30

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

Do you fight for your BUG?

2009-09-14T01:07:00.000+05:30

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

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

2009-09-13T21:51:00.000+05:30

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

Context Driven Testing (arguably be called agile testing)

2009-09-07T00:05:00.001+05:30

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:

http://www.satisfice.com/blog/archives/74

http://www.context-driven-testing.com

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

Your Approach when Testing any app

2009-09-06T23:38:00.000+05:30

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

Joan finally agreed its a Bug!!!

2009-09-02T17:31:00.000+05:30

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

My Experience with BWT

2009-08-31T00:46:00.000+05:30

Well, finally I manage to attend my first session with "BWT- Banglore Weekend Testers". :) I was excited but at the same time I was busy with some other work too ..which was on "PRIORITY". I had to multitasking but it worth a lot..... to attend the session and to listen to others and what issues they come up. The session shoot up at 9:30 PM sharp...so appreciated the punctuality.... :)

Mission!!! Find Bugs.

AUT - Google Calender.

Scope of Testing - Exploratory....find bugs.

Brwosers - whichever available with you.....

Time Duration - 1 Hr....for testing and 1 Hr for discussion on the review of the task performed.

I started testing "Google Calender" in FF.....although I am lover of Google Chrome....but I said to myself ...its Google product ....so it should work fine in Google Chrome ...so let me check in some other browsers......I open my FF and enter the url.....and login. Got to go ===> Arrh!!my mobile rang.....it was my Brother's call from US ...so can not let it go. I very much focused on the task.....and once I am done with the call....I started sharing my issues with others in the Group. But, I said to myself its better I first finish the testing and latter discuss the issues come across. I set a target of 5 bugs for myself......as I thought to myself Google is very much stable ..they are not new in the market....so I get 5 bugs......I am very much happy but if I get more.... no problem. Well to be honest and no hard feeling for anyone....but AUT .....was very "average" ...its not that friendly I expected.

=>Some of the issues to mention - Warning message if you set a reminder for a task, it should it should be "information" message and not warning.

==> You can set reminders or create appointments for the date passed by like 10th June, 2009...it is gone...so I should not be able to create new appointment on that day.

Once the time is over for testing...part we all started discussing about the experience......

I got some things like:

==> BWT - I come across some people......whom I do not know but now we know each other

==> Others sharing their approach about testing - what was their goal? How did they do that?

==> People's opinion whether the product can be used or would you recommend the product to others.

Discussion part was really excited but as you know when you are in a Group .......everyone wants to say something or the other...so somewher we lose the connection. However, people were really coming up with their experience and some other things ...rating and all. I did mange to speak some words...... :) I did ask others to vote for and against the product.....where I could see majority people were saying that the product was "average" but they will go with it so did I.

I must confess one thing over here......I wanted the discussion to be more "constructive" and "conclusive" rather than discussing why you think like this? what made you feel so? and all. If we get a constructive discussion...it has altogether different meaning.......it would have been seriously fun but at the same time a good learning point!

On and all my experience was good but I expected more. Well, this is not the end of the world guys.......I am sure that in coming weeks we will come up strong and emerge as a strong "Group" where you get a good chance to have fun, learn new things, different perception, different approaches, startegies (if any).etc.......

I am waiting for the next session - BWT..... get me in!!!!

Best Regards,

Amit

testing is my passion!!!

http://bugteaser.blogspot.com/

Testing app in other languages

2009-08-28T18:33:00.000+05:30

As a tester we have to do so many things on our own...like prepare test pla, test cases, execute test cases, test scripts....etc and most important is documentation of all this with not missing out on "Screenshots" :)

Do we apply the same things while testing application in some other language. I know for the fact that you will be getting the requirement and scope of the testing. Can we apply the same things which we apply for any other application (which is in english language or the language you understand). Not really!!!

It takes more than that.....as we need to explore some basic knowledge of the language. What if there is no option for "English" in teh application you are testing..... so you can not check out what "any button", "any text box" means in English ....if its in some other language like Spanish, French, German. etc. You can at times use your gut feeling...as what all buttons is for......may be ..or may be not. Over there we need to use the power of internet..... use translators, use some same application like the one you are testing, use interpreters..... to make yourself comfortable.

Recently, I was testing one such application...so at that time I used my gut feeling...what this button for...and ofcourse translators. There are some messages which we feel that "Errors" but actually they are not....they are just informative message. I find this stuff more challenging as that of teh application which are in "English" which we all know. Its challenge, fun, learning new things....so my experience was awesome!!!!

Although in the start I had to face some problems....as it took time for me....to get the speed. But I enjoyed it thoroughly...... I must confess that!!

Best Regards,

Amit

testing is my passion!!!

http://bugteaser.blogspot.com

Do you exist online??

2009-08-26T23:07:00.000+05:30

They say that

"If you don't have mail id then you don't exist."

Does that mean that you do not exist if you don't have mail id?". :)

I know for the fact that this is not true but we all know the importance of having access to internet as we can so many useful things online these days. If I do not have mail id then does that mean that I do not get the access to all those these things ........of I can not use the power of "internet". Not really!!!

You still very much active online but with limited access. In our life we try to achieve maximum that is the truth. Same applies to your existance online......if you want to purchase something then you need to prove others that you do exist, if you want to book tickets online you need to have mail id, if you want to order something online then you need to have mail id etc.... There are things which you want to access then you need to have mail id.....in order to participate or rather be more active online.

These days I see people of all the ages try to get mail id for them.........I have my own laptop.....but at times I visite public places to see the craze, struggle, excitement amongst these people. At times people bug with you so many queries as they are not used to this and this is something new for them, so they have this immense excitement. :) My father had so many queries when we opened his account.....it was fun!! Now he so much used to that ......so the queries are not the basic ones so it makes me to scratch my head.

As earlier said although it won't make you "invisible" but in order to be "visible" you need to have mail id. The power of internet is immense and there are some restrictions to it.....as there are some sections which can not be accessed if you are not logged in.

So do not make yourself "invisible" by not having just one mail id (which is free) so get one....and "be visible".

Best Regards,

Amit

testing is my passion!!!

http://bugteaser.blogspot.com

Test Ideas – A Login Screen

2009-08-25T15:48:00.000+05:30

Check this out....

Crowdsourced Test Ideas - A Login Screen - by the Software Testing Club

View more documents from Rosie Sherry.

Best Regards,

Amit

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

Sach Ka Saamna - Facing the truth???

2009-08-24T19:40:00.000+05:30

Well, I was browsing through and just come across the site of "Sach Ka Saamna" show which is being telecased on "Star Plus" from Mon-Fri at 11:00 PM. I regularly watch this show and love it. :)

I feel most of you must be watching this show too....if not give it a try once. As I watch this show regularly so I know the timings too but prior to this it was being telecased at 10:30 PM so kind of I know the change in the timing.

To my surperise I saw the main landing page of the site http://www.sachkasaamna.com/ the timings at the left bottom of the page marked with "red" color is not yet updated. As always I was just searching for any feedback/suggestion link on their website.....but on clicking on the link it shows the email id where in you can send your feedback/suggestion. Without wasting anymore time as I love this show......I thought of sending an email mentioning the things which needs to be corrected. I sent two mails but alas..........there was no reponse from them. I was just thought that they would not mail me but rather they would fix the thing on their site rather.........I opened the same page after few days.........its the same (no change). From users perspective these all things does matter a lot.......what if I am a new user and do not know the site of "Sach Ka Saamna". I open "Google" my favorite search engine....and type "Sach Ka Saamna" .....the first result is this site. I got happy.....I clicked on the link....and I found that the timings is 10:30 PM. Arr!!! looking at my watch I found that its 11:15 PM...so I make a note of it so that I can watch the show the next day. The next day I put on the "TV" at 10:30 PM and put on "Star Plus" .....but I see that at that time some other thing is coming up on the "TV" and not "Sach Ka Saamna". I face the truth....disappointed.....do not know what to do.....I put off the "TV" ...go to bed....crumbling. :( Now if this kind of user experience does not hamper the rating much....because of the large audiences but if you see 5% users missing the show because they are not updated of the show timings.

Does this 5% users matter to "Star Plus" or even for the matter "Sach Ka Saamna"?

This question is subjective one and the answer can vary......based on the users experiences. Somebody will say that check out in the newspaper, in ads, with friends.

This task is very simple and does not cost more to the site developer .....so why not to have updated information on the site?

The next time I will write this on "Rajiv's" blog to make him aware of it......as it seems that "Star Plus" does not have any problem with this.

Sach Ka Saamna - Facing the truth? What do you think that the reason behind not updating the timings? As I am clueless........... :) but I love the show.

Best Regards,

Amit

Testing is my passion!!

http://bugteaser.blogspot.com

Screenshots/Video ...why do you use them?

2009-08-20T22:57:00.000+05:30

As a tester everyone feels that they need to backup their bugs by giving screenshots or videos or movies which makes it easy for all to see what the tester is pointing at. I believe in documenting each and everything in detail so I always backup myself with stuff which can help me if something goes wrong!!

I always wonder why other people (developers, management, client) are not able to reproduce the bug even though you have given all the steps in detail. :) I am not saying they have to but is it that difficult to make out or reproduce the bug after detail explanation. I believe its a combination of both sometime people goes for the easy way where in they just make out the bug after watching the screenshot and some people likes to backup their detail explanation with screenshot or videos. There are times when you backup your bug with screenshots/videos does not makes things clear so there Tester has to come into the picture and reproduce the bug again.

Do you use screenshots/videos because you want to make things easy for others?

Do you use screenshots/videos because you like to use them?

Do you use screenshots/videos because you want to backup your bug?

Do you use screenshots/videos because you feel that your detailed explanation is not enough to reproduce the bug?

Do you use screenshots/videos because you feel that you can not communicate the things well?

Do you use screenshots/videos because you feel that they have to be used as others are using them?

Whatever may be the reason ...I will not go into the detail. But, I would like to say its always better to have them because using them add value to your bug. There is one more reason to this ..if you can not communicate things well so its better to use them. We can argue that testers has the responsibility to report the bugs and developers has the responsibility to fix them. There are other modes of communicating like email, chat or some other modes. What if I do not use screenshot/videos and just go to my 'pal' and explain them the issue. This kind of attitude may work or may not! We have to understand one thing that the things should be transparent for the people (management, clients, and developers).

Like I said every organization has their own way to work. There are people with differnt attitude, approaches and different point of view so at times it becomes need of the hour to make some adjustments. If you are not used to it but because your company asks you to have an organized structure ....see to other side of ......its for good sake of yours. I always recommend to have screenshot/videos to backup and it becomes easy to figure out the issue too.....for the tester also.

I leave it to you guys as I have already shared my thinking with you.

Best Regards,

Amit

http://bugteaser.blogspot.com/

Inconsistency of link of a website not a part of Usability Testing?

2009-08-18T23:55:00.000+05:30

Well, this is very funny and interesting too. I have this habbit of reviewing/testing any site which I come across. Whenever I see something weird or something which is not looking good or needs to be changed, I make a point of it and drop a mail to the concerned person if they have provided any feedback section.

This incident is part of the same story..... I was reviewing/testing some site (I can not disclose the name :)) The site was good in look'n'feel, it was user friendly and easy to navigate. Arrh!! there we go I see one link which was under "Copyright" information. The link was mainly related to terms and conditions for any web portal or any site. I saw that the link is inconsistent with that of the other links on the page. It was not following the same style as the rest all link were. However, when I clicked on the link it used to redirect on the proper page where it is supposed to go. Question comes to my mind......the link is not going with the rest of the other links on this page (as per Usability point of view that needs to be changed) but on the other hand it was going or it was opening the right page (so functionally it was working fine). I somewhat confused whether this issue will come under Usability or Functionality. :( Finally, I let it go....because I do not have to categorize this as I was not reviewing/testing for any client wherein they have asked me to generate the report in the proper format. I feel good.....that I do not have to scratch my head anymore...

As always I took a screenshot of it.....put a note against it (mentioned what I felt was wrong with the site). Once I was done.....I shoot the mail as the site has a link for feedback or suggestion. I was pretty happy and sure that I will get some reponse for this. :)

The next morning I was surfing and alas!!! I got a mail....which I desperately waiting for. I was so sure that the mail would contain this and that.....so I was in own world. Once I opened the mail I was shocked :( the customer or the person who replied to my mail has made me cry (not exactly). The mail says "Thanks for your suggestion and we appreciate your efforts for the same. However, we see that the link is not proper or inconsistent with the rest of the links on that page but it is doing its job. When a user clicks on the link they get what page they are suppose to get."

I close the mail and started doing the work I was doing. Alas!!! but I can not get rid of the thing that easily......as questions were floating in my mind like anything.

Does this not come under Usability Testing?

Is it good if the formatting of the links is not proper but functionality wise they are working proper.

Was it an issue that needs some attention (it was low severity low priority bug) as per my understanding? any many more......

There have been some good amount of time has passed by......and still the page has the link with the same formatting and all.

Does Usability always comes after Functionality or is there any time vice-versa?

Best Regards,

Amit

Testing is my passion !!!!

http://bugteaser.blogspot.com/

Usability Testing Overview

2009-08-15T17:19:00.000+05:30

I will start with a quote which says "I believe in God, rest all I test" ...Isn't it true for testers? I believe in this and I am sure many of us fellow testers will agree with me on this. When I say testing ...we have so many information available on the net so why this blog is interesting. To answer your question in simple and clear manner I will just elaborate on one type of testing which is "Usability Testing".

As a human being we all have different tastes, different attitude to see a thing, differences in our opinion, different approaches, different tools, and ofcourse different way of looking at it. Usability Testing is very important in any application (desktop, web, mobile etc.) but my fellow testers will have better idea on this ....as to how much time we all get for Usability Testing. I will not confuse anybody but note down some simple questions which comes to my mind when I hear "Usability Testing"

(a) What is Usability Testing?

(b) What all tools are available?

(d) How do we do Usability Testing under tight schedules?

(e) Why not ask for end user's feedback than doing Usability Testing on our own?

(f) How to read the mind of our customers when they have not provided with any specification?

the list goes on.......

I must say one thing the trend is changing and now the companies also making a note of it that they should give sufficient time and consult expert for Usability Testing. It is more important because "what looks good, sell easily..." . The application any type should be user friendly as your target audience is very important while performing Usability Testing. If you are testing any website which is for kids so obviously it should have more pictures than text but at the same time it should convey the message. If the desktop application you are testing is targetted for the audience which falls in the category above 50 then you have make sure that things are pretty clear... like text readability, font size, font color, flow of the application etc. These people wants to have things done in less clicks as they are not that user friendly with computers. So, before starting any testing for Usability the tester has to consider the following things:

(a) Application Type..

(b) Target Audience...

(d) Navigation/Flow of the application...

(e) Requirements of the clients (if given :) )...

These days there are tools available for Usability Testing...but as a tester we have to read others mind (customers/clients/management/end user). When you do your basics right ....things will fall in place properly. A tester has to draw a plan as how they will go about it. Usability Testing is not a thing ......that it can be done at any time. You have to be well prepared with the data to justify things to developers/designers as you will be working in parallel with these people. The important aspect of Usability Testing is well prepared plan, tools used (if any), screenshots, and comparison with competitors. It is always recommended to all to do basic study first before jumping into the world .....where you will be responsible for whole look'n'feel of the application.

Consider following things which may help you to prepare you in a better way:

(a) specifications from the clients

(b) designers/developers input...

(d) navigation of the application...

(e) color schema...

(f) consistency of the font style used.. etc...

Lastly, if you have a plan ready in advance then discuss it with your management, clients so you can ask for the time you need to carry out these tests. This way it will really help you to carry out your tests on time and make it more efficient...at the same time no compromise on the "Quality". Usability Testing is an important aspect of whole development of the application....so you need to be very careful. If this goes well then you have better chance of selling your products to more audience....which means more revenue...means more customers.....means their different views.....which is not easy to satisfy everyone. Usability Testing is no about what do you think is good or bad.....its about collection of the things like your opinion, your audience, your customers, your development/design team...these all people contribute in this. I know its not easy to satisfy everyone but if we can convince others as what do you think is good for the application...then I am sure others will agree with you.

If it is carried out in a better way then chances are more that you are coming up with good application. Usability Testing is not only about see the things as they looks...but its about how better it can look?

Best Regards,

Amit

Testing is my passion !!!!

http://bugteaser.blogspot.com/

bugTeaser!!!

A year gone by, a year ahead!! [Happy New Year - 2012]

Sunday Jinx with some false claims.

A Friday RANT

My Guest Blog Post on in-built feature for logs for Mobile Application

I don't see any error here.

Freaking gadgets.....

Correcting the mistakes...

Lesson learned series #2

*50th* Weekend Testing Session...

Expecting the unexpected!!!

Twitter services unavailable!

-Conversion error-

Lesson learned series #1

Testers do not assure the quality.

Communication: A bridge or barrier?

Resolved. Please check the note.

An apology to all!

Importance of being original!

Keep the error message SIMPLE.

Can you fix that issue now? :-)

CAPTCHA! Why you're not in CAPS?

I'm not responsible for that.

Do you still stick to best practices as an "Expert"?

Can you test the application completely?

I speak for the user.

Halloween Scary tale!

The networking is invaluable

What do you get going day in day out?

Why the error messages does not stick to their places?

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

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

Do you fight for your BUG?

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

Context Driven Testing (arguably be called agile testing)

Your Approach when Testing any app

Joan finally agreed its a Bug!!!

My Experience with BWT

Testing app in other languages

Do you exist online??

Test Ideas – A Login Screen

Sach Ka Saamna - Facing the truth???

Screenshots/Video ...why do you use them?

Inconsistency of link of a website not a part of Usability Testing?

Usability Testing Overview

50th Weekend Testing Session...