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

0

Posted by Amit Kulkarni [Admin] | Posted in , | Posted on 1/01/2012 12:00:00 AM


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

Reactions: 

Sunday Jinx with some false claims.

2

Posted by Amit Kulkarni [Author] | Posted in , , , , , | Posted on 9/04/2011 10:18:00 PM

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.

Reactions: 

A Friday RANT

0

Posted by Amit Kulkarni [Admin] | Posted in , , , , , , | Posted on 8/27/2011 04:20:00 PM

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]

Reactions: 

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

0

Posted by Amit Kulkarni [Admin] | Posted in , , , , , | Posted on 8/04/2011 09:39:00 PM

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

Reactions: 

I don't see any error here.

2

Posted by Amit Kulkarni [Admin] | Posted in , , , , , | Posted on 5/18/2011 05:29:00 PM

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

Reactions: 
Subscribe to: Posts (Atom)