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
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.
A WIP schedule will be up on the Droidcon India website and will be updated periodically.
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:
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.
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.
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.
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
Submitted Sep 30, 2013
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:
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)
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.
Hosted by
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}