Test-Driven Development on Android with the Android Testing Support Library (Google I/O ’17)

By | December 11, 2019


17 thoughts on “Test-Driven Development on Android with the Android Testing Support Library (Google I/O ’17)

  1. Saravana Thiyagaraj Post author

    At 35:10, there is a reference to `Injector.getNotesRepository()`. Is this from Dagger? Would love to get my hands on this sample code. Github link?

    Reply
  2. soundiscomforting Post author

    What about @MediumTest? And you're saying that mock static is bad, but you're mocking static in the example project! Please, advice

    Reply
  3. 罗力 Post author

    every developer should know how to use tdd…

    Reply
  4. Arturo Mejia Post author

    Nice Android Testing T-shirts 31:25. Where I can buy one?

    Reply
  5. Igor Ganapolsky Post author

    Is there an official code repository from Google where they demonstrate using Robolectric for Android testing?

    Reply
  6. Nocrii Post author

    16:59
    Didn't you mistake the id from which you take text? 😛

    Reply
  7. Mahesh Bhalerao Post author

    I'm new to write tests. I've created two test classes for testing my 2 different activities. Could anyone here tell me, how to invoke one test class from another test class without closing the application.??

    Reply
  8. ryanrunss Post author

    This talk was awesome and I love those t-shirts!

    Reply
  9. Kim An Post author

    Developer family? What is google's definition of family?

    Reply
  10. Network Ninjas Post author

    https://youtu.be/pK7W5npkhho?t=1016 Shouldn't it be R.id.title ?:)

    Reply
  11. Marta Baena Post author

    Great video! I hope our interview to an Android developer of a startup can help! https://wavefindyourfriendsblog.com/2018/06/22/wave-interviews-android-developer-francisco-moya/ thank you!

    Reply
  12. Patrick Jonas Post author

    https://www.youtube.com/user/androiddevelopers/about

    Reply
  13. リョウヘイ Post author

    "Integration Testing" "UI Components"

    what? Why am I even watching this crap?

    Reply
  14. virlsh Post author

    Because of 28:45 robolectric async testing is broken fundamentally. Learn from Apple and XCTestExpectation!

    Reply
  15. Rakhi Dhavale Post author

    TDD really saves a lot of time if followed properly.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *