Dev fest2015androidunittestingbyoyewaleademolasao
•Descargar como PPTX, PDF•
1 recomendación•139 vistas
The presentation given on Android unit Testing with Android Testing Library. Presentation given at the GDG DevFest SouthWest Nigerian meetup.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (18)
Destacado
Destacado (9)
Similar a Dev fest2015androidunittestingbyoyewaleademolasao
Similar a Dev fest2015androidunittestingbyoyewaleademolasao (20)
Último
Último (20)
Dev fest2015androidunittestingbyoyewaleademolasao
- 2. What is Testing? Software Testing is an investigation used to provide stakeholders about the quality of the product/service under test.
- 3. Why should we automate Tests? -- It gives us confidence to make changes. -- They are the guardians of our code.
- 4. What types can we use? 1. Unit tests 2. Integration tests 3. Acceptance tests 4. Performance tests
- 5. What is Unit Testing? A unit test is a test that can verify that all of the code in exactly one non-trivial class is working correctly. If this test fails, we know that the problem is located in that class being tested.
- 6. Android Unit Testing Frameworks… -- Android testing framework -- Roboelectric -- Robotium
- 7. Unit Testing Like Insurance Policies. A lot of Effort for something you will never use. They cover what you use in advance.
- 8. Let’s get our hands DIRTY!
- 10. “Start testing and let us all sleep well.”
- 11. Remember :: It should be the first line of defense. No side effects (no I/O, network, database etc.).
- 12. References Official Android Developer Docs. Hello, Startup by Kevgeniy Brikman 1st ed. Android Unit Testing Framework Overview https://www.captechconsulting.com/blogs/android-unit-testing---framework-overview Android I/O 2015 Code Lab https://io2015codelabs.appspot.com/codelabs/android-studio-testing#1 Software_Testing ( https://en.wikipedia.org/wiki/Software_testing )
Notas del editor
- 1. Unit tests (They verify the functionality of a single, small "unit" of code). 2. Integration tests (Verify that multiple units work correctly when put together). 3. Acceptance tests (Verify the behavior of the product from the perspective of the customer). 4. Performance tests (Verify the stability and responsiveness of a system in the face of heavy load and failures.)
- It should be the first line of defense They should have no external dependencies They should not have side effects ( no reading or writing to disk, no network calls, no database calls and no access to global state).