Stop Worrying about Unnecessary Things When Testing a Mobile App
summary
Introduces a testing approach for mobile apps that improves test stability and execution speed while simplifying test data creation by replacing backend services with mocks. Demonstrates using Java and the open-source WireMock library to emulate backend services and dynamically create test data, including a live demo of the technique.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:17Mobile testing without mocks
- 5:16Project structure with Ermak
- 6:21Mock creation process
- 8:54Why Ermak mocks
- 10:36Simple mock servers with Ermak
- 12:28Complex testing scenarios
- 16:56Mock responses from contracts
- 19:15Backend artifacts for mocks
- 21:10Unit tests for mocks
- 22:58Mocks across platforms
- 24:03Mock server startup time
- 24:45Mocks pros and cons
- 26:34Mocks implementation effort
- 28:00Faster stable testing
- 29:47Better testing process
- 31:17Optimizing test coverage
- 33:06Collaborating with backend
- 35:05When mocks are effective
- 36:54Frontend-backend collaboration
- 37:38Dynamic mock generation
- 38:29Capturing real server responses
- 39:11Q&A
related talks
48mTesting Mobile Apps When Creating Test Data Is Impossible
41mAdvanced HTTP Mocking with
31mModern Testing Tools for Java Developers
24mMastering the mobile testing pyramid
38mDoublers in Tests. Wiremock vs Mockito
31mThe power of mocking APIs
57mModern Testing Tools for Java Developers
18mCommon pitfalls in mobile testing