Mobile applications are complex software systems. Automated tests can help to ensure reliability, which leads to satisfied customers - an essential ingredient for any successful product. What if you could write tests that document requirements and features in a way that everyone involved in a project could understand? If tests
read more →

Controlling any peripheral device from an Android Things board requires a driver. If no driver is available it's down to you to write your own. Once that's written, how do you know it will keep working? You need to test it. Let’s take a look at unit testing for
read more →

Android Things is a lightweight version of the Android operating system that can be installed on IoT-focused devices. Android Things includes 'user drivers' functionality, enabling developers to easily control a wide range of peripherals (LEDs, switches, buttons, servo motors etc). Let’s take a look at what it takes to
read more →

Google has just announced the amazing Android Things. This gives the Internet of Things (IoT) a real jump start with the availability of the Android ecosystem and all the open source code and ready to use libraries that go with it. You'll want to start creating an IoT Android Things
read more →

In the previous post, we wrote the acceptance test as a first step and started creating the most external classes of our implementation. In this post, we will finish implementing the system, and will summarize what we have learnt during the process. To finish the BankAccount class, we need to
read more →

In the previous post, we introduced the Bank kata. We explained how we are going to implement it in Android, reviewed the different kinds of tests that we use in Outside-in and transformed a user story into a bunch of acceptance criteria. In this second post, we will focus more
read more →