O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Android Testing, Why So Hard?!

1.784 visualizações

Publicada em

Android devices come in all shapes and sizes, with varying performance levels and APIs. This is one of the reasons that writing tests for Android applications can be so daunting, let alone the seemingly endless number of tools available to write those tests. This presentation discusses three simple steps to get started with writing tests for your Android applications.

Publicada em: Engenharia
  • Seja o primeiro a comentar

Android Testing, Why So Hard?!

  1. 1. ANDROIDTESTING, WHY SO HARD?! Annyce Davis - @brwngrldev
  2. 2. Quick Poll @brwngrldev
  3. 3. WHY SO HARD? • too many devices • tight-coupling • too many options Courtesy of TechStage on Flickr @brwngrldev
  4. 4. @brwngrldev
  5. 5. @brwngrldev
  6. 6. Use JUnit for POJOs and Helper Classes @brwngrldev
  7. 7. @brwngrldev
  8. 8. Use Robotium for Integration Testing @brwngrldev
  9. 9. @brwngrldev
  10. 10. @brwngrldev
  11. 11. @brwngrldev
  12. 12. Use Monkey to StressTest @brwngrldev
  13. 13. @brwngrldev
  14. 14. GETTING GOING @brwngrldev
  15. 15. RESOURCES • List of Articles/Videos: http://git.io/h6HQ • Fragmented Podcast: Episode #1 • Android Workflow Guides: http://git.io/h67r • Genymotion Emulator: https://www.genymotion.com @brwngrldev
  16. 16. “Spend time writing tests now, or spend more time fixing bugs later… your choice” @brwngrldev