This week I gave a talk to Londroid testing enthusiasts on how we do TDD on Android at TouchType. Our system uses RoboGuice (an Android version of Google Guice) and an open-source Scala mocking framework called Borachio, developed by Paul Butcher, our Chief Software Architect. We write our tests concisely, in Scala, and we […]

As we saw in part 2 of this series, mocking Android’s PowerManager service directly is impossible. But there is an alternative approach that gives us something close enough. This article describes that approach.

In part 1 of this series, I showed how to mock an interface that we created ourselves under Android. That’s useful, but mocking really pays dividends when mocking OS services—doing so allows us to test our code in isolation, verify that it interacts with the OS correctly and that it handles errors properly.

In the next few “Technical Wizardry” articles, we’re going to look at the approach we’ve developed to help with testing Android code (first published here).

Welcome to the new “Technical Wizardry” section of the TouchType blog. Here’s where we’ll be sharing a few of the tips and tricks we’ve learned while developing SwiftKey and the Fluency prediction engine that underpins it. We’re going to start off with a series of articles on Android development (originally published here).