Move from Inbox

Move from Inbox

A Beginners Guide to an Effective Android Testing Strategy

Why testing?

deliver to the QA team only good tested code, which should normally not have any bugs
testing improves the design and modularity of our code base
testing helps us to implement “Continuous Integration”

Types of test

Unit tests (JUnit)
Integration tests (Instrumentation tests → Espresso, Automation tests → UI Automator)

Architecting the app for testing

Using Model-View-Presenter pattern is good choice to “modularize” the app. This will make the testing much easier (we can test each layer separately).

Test pyramid

The “test pyramid” : Acceptance - 10% Integration - 20% Unit - 70%

This pyramid makes sense because: * integration tests are complexer * integration tests takes more time * if an integration test fails, we have much more things which can go wrong Implementing Unit tests Use Mockito to mock dependencies. Project structure: * Unit tests live in the folder “test” * UI test are located in “androidTest” Anatomy of a Unit Test * @RunWith(MockitoJUnitRunner.class) Here is specified the runner which should be used to run the test * @SmallTest, @MediumTest, @LargeTest @SmallTest is normally a Unit test, @MediumTest test more than one module, @LargeTest is usually an UI automation test * @Before Marks method which should be runned every time before a test is launched * @After Marks method which should be runned every time after a test to release resources, close files etc. * @Test This define a test method. It usually should follow the “Arrange-Act-Assert” pattern: – Arrange all necessary preconditions and inputs. – Act on the object or method under test. – Assert that the expected results have occurred. Running the tests Use “Unit Test” on Build variant menu. After this right click on the Test package folder and then on “Run tests…” (or Debug or Run with Coverage) Implementing Integration Tests In this article using Espresso. <Example>…

https://davidguerrerodiaz.wordpress.com/2016/03/04/a-beginners-guide-to-an-effective-android-testing-strategy/