Testing: why, when and how?

Best Practices / Code Quality
06/17/2016 -
14:00 to 14:45
Stage 2

Session abstract: 

Unit testing on Android is still quite new - two years ago, projects with good tests were quite rare. Even today writing and maintaining tests seem like an unnecessary chore to some, but this doesn't need to be the case.

I will present my point of view on how writing test code can be as fun as writing a shiny new feature!

I would like to talk about how software tests are not an annoyance, but a way to improve oneself as a software development professional, by providing proof that your code does exactly what you’ve intended.


A brief overview of the presentation content:

  • Some of the reasons Android developers use to avoid testing

  • When tests should and should not be used

  • Why code coverage percentage is a meaningless indicator of code quality

  • How testing can help improve your project's architecture

  • How to use your tests as both the specification and the verification with TDD

  • How testing can help with hard-to-debug code, such as when using declarative RxJava


After the talk I would like to gather feedback and talk with the audience about their take on testing.

Session Audio: 

Session Slide: