143: Real world testing thoughts

In this mini fragment, Donn and Kaushik share some thoughts on real world testing with Android development – a favorite topic of theirs.

Kaushik recently ran into a case where an espresso test fails because the UI stops performing. It’s an interesting discussion on figuring out what matters when you write your tests. They dive into strategies and techniques around testing. What makes a good test, what should you be testing?

They then talk about why Hermetic testing is pretty hard on mobile and ideas around a simple solution that could be provided out of the box. They then round it up talking about TDD and it’s role in today’s world.

Hope you enjoy this one!

Download

Shownotes

Sponsors 🙏

Contact

142: Indie development on Android and iOS with Matt Logan

In this episode, we talk to our friend Matt Logan. Matt took some time off and worked on an indie app called Sessions. He built this for both Android and iOS. In this episode we talk to him about his experience building apps on both platforms, techniques, advice and other good stuff.

Download

Shownotes

Sponsors

Contact

141: Impostor Syndrome

In this mini fragment, Donn and KG talk about Impostor syndrome. Most of us developers are plagued by this. Does this feeling ever go away? How do we deal with this? Listen to this short episode to find out more.

Download

Shownotes

Sponsors

Contact

140: ProGuard with Jeb Ware

We all know of ProGuard, we want to use it and like it. But let’s face it proGuard ain’t pretty. In this episode we have Jeb walk us through the magic of ProGuard.

We talk to Jeb Ware of American Express. Jeb works as an Android developer and has given some great talks on ProGuard. He walks us through what ProGuard is, how it works, advancements with R8 and more.

By the end of this episode, you should have a new found appreciation for proGuard and bravely approach adding proGuard to your projects.

Download

Shownotes

Contact

139: Static code analysis with Manu Sridharan

In this episode, Donn and Kaushik talk to Uber’s Manu Sridharan on static code analysis. Manu’s a badass who did his PhD on the subject! He explains how static code analysis works, how Uber leverages these tools in their app development pipeline and how we can use such tools to build high quality Android apps.

Download

Shownotes

Note from Manu:

I found the story I was thinking about: Reed Hastings founded the company that built the Purify tool for debugging memory errors in C programs before founding Netflix. But, that’s actually not a static analysis tool; it does dynamic analysis by adding extra metadata at runtime.

As far as the history of lint goes, from Wikipedia looks like Kaushik’s guess was exactly right as to why it’s called lint. Looks like the name goes back to the late 1970s.

Misc

Contact