bugTeaser!!!

Love teasing bugs!!

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