- [Instructor] So far we have written JVM Unit Test,…Instrumentation Unit Test, and Instrumentation UI Test.…We have learned that instrumentation tests are slower to run…because we need to deploy our code to a device.…We can test the part of our app that does not use…any Android class on the JVM,…but if you want to test the UI,…we need Android.…Is there a way to test the UI on the JVM?…Yes.…
We can use the MVP pattern.…MVP stands for Model, View, Presenter.…It is an architecture pattern that…puts an interface in front of your Android UI code,…and puts out all significant logic…to the pure Java side of the interface…in an object called the presenter.…You write JVM unit test to test this presenter,…and mock the interface representing the Android side.…This way, you test all the logic pertaining to changing,…and interacting with the Android UI via the interface…without actually touching Android code.…
And therefore, can run everything on the JVM.…Next, we are going to use…the MVP pattern for our recipe app.…
- Why test?
- Local vs. on-device
- Code coverage
- UI testing
- Hermetic environment
- Dependency injection
- Testing with MVP
Skill Level Intermediate
1. Testing Considerations
2. Test as You Go
3. UI Testing
4. Hermetic Environment
5. Robot Pattern
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.Cancel
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.