Android Testing

October 15, 2014

I’ve recently started looking at the Android testing framework and once again I have to say I like it, I’m impressed with the set of tools available.

I won’t say too much about it as it’s covered pretty comprehensively in the Android documentation here: (note some of this stuff, namely the tutorial is pretty out of date, SDK 8, but it is still valid), and here:

What I will say right now is that if you’re not testing your code as soon as you begin writing your code at the very latest (many proponents of Test Driven Development advocate writing your unit tests before you start writing application code) you should be, really, you should (I intend to make the case for unit testing in another post sometime).

The Android SDK tools make it really easy to start testing, they provide everything you might need in terms of base test classes, mocks, instrumentation and automation. The documentation gives guides on what to test and how to test.

With all of these tools built into the SDK it would be foolish not to use them. If you’re new to Unit Testing and Software Testing in general I think this could be a really good place to start.

For me personally, having such a comprehensive framework in place immediately removes any barriers to unit testing (Unit Testing can be hard at times :(, sometimes it seems that I put more time into writing tests and the conditions under which they can run than actual application code), quite simply there are no excuses for me not to do it here.

Some things what I likes:

  • Familiar – Based on JUnit, anyone who has used JUnit and it’s test runner should be comfortable straight away.
  • Built in Instrumentation for testing Activity lifecycle and UI components – To try to do this from scratch would be incredibly tedious.
  • Comprehensive mocking framework – There is a good set of system mock objects that can be used for dependency injection. Often external dependencies of classes can cause difficulties in testing, providing mock objects helps alleviate this, having a ready made set of mocks to extend is very helpful.
  • UI automation – Great for automated system/functional testing, anyone who has had to run manual regression tests on Software UIs will appreciate this.

Me and the IDE

September 25, 2014


I’m just going to come straight out and say it. I love using modern IDEs.
Yes, I’m sure I can write code just as well in a plain old text editor with a bit of code highlighting, yes, I’m sure Emacs can do everything my IDE does and so much more, maybe real developers use Vi(m), (Vi, don’t get me started, Emacs I can handle but Vi, really, why? Ok maybe cos I’m too lazy to learn how but that’s kinda my point), maybe all that IDE clutter distracts from the purity of the essence of distilled code.

Maybe, but I just want to get stuff done. I’ve worked with nothing but Emacs, a console and the GNU tool chain developing c/assembly applications for embedded Motorola 68000 based chips, it worked, it was actually quite fun because it demanded an intricate understanding of what was going on, from the workings of the tool chain on the development OS right down to the hardware level of the target, but man was it tedious.

No, give me my comfy chair of an IDE, take away my code completion and I’ll start to scream, and maybe punch something.

Currently eclipse is my tool of choice, I like it, it’s easy to use, highly extentible, well supported by the software community, and free.

I’ll admit that I actually enjoyed using Visual Studio 2010 (the last version I used) and was a bit sad when I moved to Java development (although why the f**k does an installation of VS take up more space than the operating system, around 6Gb, wtf!! I reckon they’re just writing a load of random ones and zeros to the hard disc to make it look big to justify the cost 🙂 ).

Ok, there is a good argument that too much hand holding causing a dumbing down of software development (see this excellent article by Charles Petzold, but surely it comes down to using the tools available the way that’s best for you, not letting the tools lead you.