hudl 2 tablet by Tesco


After the huge success of hudl 1, Tesco launched its bigger and better second generation Android tablet to the public on the 9th October 2014. Since its launch the hudl 2 has been getting a lot of positive feedback. You can read more about the hudl 2 specs and reviews from the Tesco direct website. Alternatively just do a search on Google (or click on this link) and read the reviews.

During my time on the hudl project I had 2 main roles in the team. My first role was to be part of the app development teams for Top apps and Get started, where I would undertake all the testing duties such as writing test cases, manual testing, writing automated tests and attending project meetings such as retros, sprint kick offs and daily stand ups.

  • Top apps is similar to the Google Play store where you can find a whole host of great apps and games to try with your hudl.
  • Get started app gives users handy tips and tricks to help them get the most from their hudl.

My second role was to write automated tests using UiAutomator for the hudl tablet which we could run on a daily basis. This involved writing tests both for the device hardware (Such as Wifi and bluetooth) and the software which was pre installed on the device, both Tesco apps and standard android apps (for example Top apps, Get started, Camera, Gallery, etc).

As I had already written some automated tests for hudl 1 I decided to use our existing code and framework so regardless of the device in test (hudl 1 or hudl 2) the automated tests would work seamlessly despite having different versions of the OS and api levels (hudl 1 being on Jelly bean (android 4.2) and hudl 2 being Kitkat ( android 4.4)) as well as the different screen size and apps which have been pre-installed on the device.

To give us better testing coverage we explored new methods of performing certain actions. For example at the start and end of every test we perform a setup and tear down so that the device / app is at a “fresh” state. In order to reduce the test time and avoid the risk of the test failing at the setup and tear down phase we would use ADB (Android Debug Bridge) commands to clear app data instead of going to Settings > Apps > All apps then finding the app and clicking on the clear data button.

At the time of writing this we have around 400 automated tests running on a daily basis on multiple hudl devices. These tests have allowed us to deliver products faster and with more confidence.

Leave a Reply