Unit Test your Android application using Robolectric

Nov 2013

25 Mon

26 Tue

27 Wed

28 Thu 10:45 AM – 05:30 PM IST

29 Fri 10:45 AM – 06:45 PM IST

30 Sat

1 Sun

Make a submission

MLR Convention Centre, Whitefield, Bangalore

About Droidcon

Droidcon is India’s largest Android developer conference, and is part of the world wide series of conferences that happens in London, Paris, Berlin, Netherlands, Tunis, Ankara and Brussels. If you are doing anything with Android, you’d want to be here in Bangalore on Nov 28-30th 2013.

Schedule

A WIP schedule will be up on the Droidcon India website and will be updated periodically.

Selection Process

Voting is open to attendees who have purchased event tickets. If there is a proposal you find notable, please vote for it and leave a comment to initiate discussions. Your vote will be reflected immediately, but will be counted towards selections only if you hold a ticket. Proposals will also be evaluated by a program committee, consisting of:

Aravind Krishnaswamy of Levitum is the Program Chair
Amrit Sanjeev of Intuit and Blrdroid will run the App Demos track.
Kumar Rangarajan of LittleEyeLabs will run the Systems track.
Rahul Gonsalves of UnCommon will run the UX track.
Aravind Krishnaswamy of Levitum will run the Business track.
Ravi Korukonda of PurpleTalk will run the Gaming track.
Soham Mondal of Triveous and Blrdroid will run the Workshops.

Proposers must submit presentation drafts as part of the selection process to ensure that the talk is in line with the original proposal, and to help the program committee build a strong line-up for the event.

Milestones

Final date for submission of proposals Oct 18th, 2013.

First set of pre-confirmations Oct 18th, 2013.

Submission of slide drafts Oct 25th, 2013.

Second set of pre-confirmations Oct 26th, 2013.

Schedule draft posted on site Nov 4th, 2013

Final confirmations Nov 5th, 2013.

Final schedule Nov 8th, 2013

All speakers are requested to be available for officehours during the conference. This will be a scheduled 30 minute block of time during which attendees can meet you at a designated space for open Q&A offstage.

There is only one speaker per session. Attendance is free for selected speakers. HasGeek will cover your travel to and accommodation in Bangalore from anywhere in the world for speakers delivering full sessions (30 minutes or longer). As our budget is limited, we will prefer speakers from locations closer home, but will do our best to cover for anyone exceptional. If you are able to raise support for your trip, we will count that as speaker travel sponsorship.

Commitment to open source

HasGeek believes in open source as the binding force of our community. If you are describing a codebase for developers to work with, we’d like it to be available under a permissive open source license. If your software is commercially licensed or available under a combination of commercial and restrictive open source licenses (such as the various forms of the GPL), please consider picking up a sponsorship. We recognize that there are valid reasons for commercial licensing, but ask that you support us in return for giving you an audience. Your session will be marked on the schedule as a sponsored session.

Non Accepted Proposals

If your proposal is accepted for a session > 30 minutes long, we will cover your event ticket.

If your proposal is not accepted, you can buy a ticket at the same rate as was available on the day you proposed. We’ll send you a code.

Tickets: http://droidcon.doattend.com

Website: https://droidcon.in/2013

Hosted by

droidconIN

droidconIN is an annual conference on Android, part of the worldwide series of events. more

All submissions

Previous Next

Unit Test your Android application using Robolectric

Submitted Sep 30, 2013

Section: Workshops Technical level: Intermediate

This workshop is for giving an overview on how to write faster, maintainable and behavioural tests using Robolectric, an Android Unit Testing Framework. At the end of the session, the attendees should be able to:

Learn about basic Android Unit Testing and understand the issues with the default AndroidTestRunner
Overview of Robolectric
How to write tests using Robolectric and run it in JVM [i.e. instead of Dalvik]
How to integrate Robolectric tests with your Continuous Integration Server such as Jenkins

Outline

Android SDK comes with a testing framework called Android Instrumentation Runner which is written on top of JUnit. The problem with it is that it is slow as it requires dexing (i.e. converting into Dalvik Executable), packaging and installing on the actual device or emulator. This can become a bottleneck as unit tests are expected to run fast.

Running the tests in the JVM is not possible by just mocking because, the actual class definitions are available only in Dalvik and not in android.jar which the SDK provides. The android.jar throws RuntimeException for all the methods, and its tough to mock or extend because of the way the Android SDK is designed.

Robolectric on the other hand has rewritten Android SDK classes so they can run in the JVM. It also handles inflation of views (i.e. creating views from the xml file), resource loading, and lots of other stuff that’s implemented in native C code on Android devices. This allows tests to do most things you could do on a real device. It’s easy to provide our own implementation for specific SDK methods too, if needed.

The workshop is intended for anyone who wants to write Android Unit Tests as FIRST (Fast, Isolated, Repeatable, Self-Veifying and Timely)

Requirements

Wisdom wise:
- Experience with Android Development
- Familiarity with TDD will be an added advantage
Hardware wise:
- You have to bring your own laptop (don’t forget the charger)
- Please bring your own Android device to test out your apps on them in real time
- Make sure your machine configuration is reasonable enough to withstand the dev environment.
Software wise:
- Operating System: Windows XP (32bit), Windows 7 (32 /64 bit), Windows 8 (64 bit), Mac OS X 10.5.8 or later (x86 only) or Linux (tested on Ubuntu Linux, Lucid Lynx)
- Eclipse IDE (or Participants can directly download platform specific ADT Bundle from http://developer.android.com/sdk/index.html)
- Eclipse 3.6.2 (Helios) or greater
- Note: Eclipse 3.5 (Galileo) is no longer supported with the latest version of ADT.
- Eclipse JDT plugin (included in most Eclipse IDE packages)
- JDK 6 (JRE alone is not sufficient) with latest update needs to be installed
- Android Development Tools plugin (recommended)
- Preferred Android SDK version is 4.2.2 i.e. API Version 17
Note: Specific libraries required for the workshop will be shared during the workshop.

Speaker bio

Leena is the Head of Engineering @ Multunus. She was bitten by the TDD bug a couple of years ago. Since then she’s moved onto Continuous Delivery (CD) in a big way - even spoke about CD at DroidCon India 2011 and AgileIndia 2012. Having done enough TDD in Ruby/Rails, Javascript/Backbone/Angular - she’s now keen on conquering the Android world.

Krishnaprasad, alias KP, is the Senior Software Architect @ Multunus. His technical expertise ranges from J2EE, Ruby On Rails on the Webapp technologies to Android Native and Hybrid apps. He is a big fan of TDD too. He has also spoken at Droidcon India 2011. He is all set to educate the world with his knowledge about the Android universe.