Android Test Driven Development

563 views

Published on

Android Test Driven Development

Published in: Software, Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
563
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
7
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Android Test Driven Development

  1. 1. Test Driven in Mobile Application Development
  2. 2. Nggak Confidance dengan aplikasinya sendiri? Break pada fungsi yang lain? Rumit dengna coding-an sendiri
  3. 3. Traditional vs Test driven development cycle design test code test code design test code refactor Traditional Test driven development VS
  4. 4. Lasse Koskela Delivering the required functionality - more time for cleaning up our code base - getting up to speed the latest development in tools an technology - more time to imporve quality, confidence and speed
  5. 5. Running tests on an Android emulator or device is slow! Building, deploying, and launching the app often takes a minute or more. That’s no way to do TDD. There must be a better way.
  6. 6. Android instrumentation test are slow
  7. 7. Robolectric is a unit test framework that de-fangs the Android SDK jar so you can test-drive the development of your Android app. Tests run inside the JVM on your workstation in seconds
  8. 8. Java Project Android.jar Robolectric .xxx.jar
  9. 9. Run Tests Outside of the Emulator No Dexing No Packaging
  10. 10. ● Iterate quickly ● Write black box style of teste ● Test behaviour instead of implementation Robolectric lets us..........
  11. 11. Study Case!!
  12. 12. Requirement User bisa menjumlah dan mengurangkan dua angka. User juga bisa meliat halaman about
  13. 13. ✔ input,button and output should not be null ✔ set default input1 and input2 as zero ✔ perform plus action ✔ perform minus action ✔ perform go to about page To be tested
  14. 14. LIVE CODE!!
  15. 15. Set up envionment create android project create java project

×