Unit testing is often omitted from the development cycle of a mobile application (unless you are working in a large team, typically). If you are not in a large team but are essentially the equivalent of the 1980s bedroom coder, why should you unit test when it’s quicker to deploy to a device and see first-hand if something fails?
The simple answer is that it is usually very difficult to find what has gone wrong, and as the code base gets larger the ability to quickly find the issue decreases significantly. Take, for example, the following: I have a database-driven application. I add code ...
