Saturday, December 28, 2013

Things I like as tester (impersonating user) about Google - A short one.

After using too much Google products and services I have realized that how much effort they had put up on grabbing such a vast number of people to use their products and services as a preferred choice. And why I think so I will share an example, as a tester, that is impersonating as an end user.

Google Translate (translate.google.com)

This is the product that I use too often while I have to see different translations for different languages (not that accurate thought :)) but it gives you enough idea about requested translation. So, I was having difficulty in grasping the word "Irony" in English to English so I picked up description of the word in English and thought of the Google Translator straightaway and before launching the http://translate.google.com the evil tester from the subconscious came into conscious mind and I used one of the way I use to join running program* with its required arguments and it was unexpected as per my evil thinking Google has tested this.

I provided the URL as <translate.google.com "Witty language used to convey insults or scorn, esp. saying one thing but implying the opposite">and rather than getting HTTP 404 or something dirty Google did it smoothly one text box contained the requested string and other contained the requested translation. 

I don't know whether Google tested this case explicitly but It took care of my expectation and you always go there where your expectations are honored.

*Running and opening file simultaneously:
 
When user want to open any file on any text editor or word processor software they usually launch the software and open file from some path, or directly go to the directory path where the file is present and double click to open it. Since I work on files that present on disparate locations so usually open the software by running it and simultaneously providing the path of the file e.g. pressing meta+R , writing notepad/winword "" and enter.

Saturday, June 29, 2013

Installation/Un-installation testing: Your first communication point with end-users.

It’s been almost a year that when I last added a blog post to Software Quality Geeks. Quickly getting towards the topic that today we will be having a look at Installation Testing. This blog post or next few ones, probably soon after this one, will have the same theme that rather than writing too much about the topic we should have a look at bird eye view of any quality or testing topic. Therefore, we will be learning at installation/un-installation testing and its coverage area with help of mind-map or brainstorming diagram.
Installation Testing is very import part of any software, because it usually requires some of sort of changes in customers or end-users machines so it must be tested carefully. Since this is the point when customer first communicates with your application, anything that goes awry at this time can cause enough damage to the business. Therefore, to avoid any potential loss to the business Installation Testing/un-installation testing should be a part of Test Plan and given enough time in testing the application as far as Installation/un-installation is concerned and for that following map can be referred and customized according the need, budget and timeframe.


The post is not open to comments, must provide your valuable ones.


Good luck for installation testing!