Today I stumbled upon this post by Adam Goucher in which he laments the lack of support for TDD for Android. I've got to say I whole-heartedly agree with his points, especially the part where he complains about the way most Android books either ignore testing completely or treat it as an afterthought.
For my own Android development I have tried the approach of dividing the application into an Android independent part which I test using regular Java unit tests and an Android dependent part which I currently test the old-fashioned way, i.e. running the app on a real smartphone and watching the logcat output. For my simple app that works quite well but it's only halfway reliable because manual tests are obviously rather boring so I tend to test only the parts I've actively changed instead of doing a full test after each change.
But at least the automated tests cover most of the inner workings of the app which is a big step in the right direction and has enabled me to add features more quickly and reliably than I could before.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment