3.2 Testing Your App.pptx - Android Developer Fundamentals Testing and Debugging and Backwards Compatibility Lesson 3 Android Developer Fundamentals

3.2 Testing Your App.pptx - Android Developer Fundamentals...

This preview shows page 1 - 8 out of 28 pages.

Android Developer Fundamentals This work is licensed under a Creative Commons Attribution-Non Commercial 4.0 International Lic ense Testing your app 1 Testing and Debugging, and Backwards Compatibility Android Developer Fundamentals Lesson 3
Android Developer Fundamentals This work is licensed under a Creative Commons Attribution-Non Commercial 4.0 International Lic ense Testing your app 3.2 Testing Your App 2
Android Developer Fundamentals This work is licensed under a Creative Commons Attribution-Non Commercial 4.0 International Lic ense Testing your app Contents Why testing is worth your time Unit testing Note: User interface testing (instrumented testing) is covered in a later chapter 3
Android Developer Fundamentals Testing Rocks 4
Android Developer Fundamentals This work is licensed under a Creative Commons Attribution-Non Commercial 4.0 International Lic ense Testing your app Why should you test your app? 5 Find and fix issues early Less costly Takes less effort Costs to fix bugs increases with time $1 Specification Design Code QA Release $10 $100 $1000 Cost to Fix Discovery Time Catch bugs early!
Android Developer Fundamentals This work is licensed under a Creative Commons Attribution-Non Commercial 4.0 International Lic ense Testing your app Types of testing 6 Levels of Testing Component, integration, protocol, system Types of Testing Installation, compatibility, regression, acceptance Performance, scalability, usability, security User interface and interaction tests Automated UI testing tools Instrumented testing (covered later)
Android Developer Fundamentals This work is licensed under a Creative Commons Attribution-Non Commercial 4.0 International Lic ense Testing your app Test-Driven Development (TDD) 7 1. Define a test case for a requirement 2. Write tests that assert all conditions of the test case 3. Write code against the test 4. Iterate on and refactor code until it passes the test 5. Repeat until all requirements have test cases, all tests pass, and all functionality has been implemented

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture