App developers tend to not write unit tests, it requires some extra setup in the beginning, but if you will be working on the app for some time, they are invaluable. Just like with any other serious engineering effort.
We're Automating user data leak detection: <a href="https://fallible.co/blog//2016/03/13/Automating-data-leak-detection/" rel="nofollow">https://fallible.co/blog//2016/03/13/Automating-data-leak-de...</a><p>Some of the tests can be generic across all the apps and may not be written by each and every tech company. We intend to automate those.
i have found that dogfooding and acceptance tests (tracking regressions), combined with focused source commits are the most practical.<p>while unit tests laser in on specific problems, they are often unnecessary and with frequent commits and sensible commit messages, the causes of problems are always trackable and nearly always obvious.<p>git bisect helps in situations where the commit count is high (in large teams).
Does runnable.com has a full Android environment setup? I wrote unit test and functional/ui tests for my android app, but im too lazy configuring my jenkins setup.