- [Instructor] We will create the class screen robot…as the basis for all robot classes.…This serves two purposes.…One, it abstracts common verifications…such as a view being not selected…from multiple calls…I.e not and is displayed…into a single convenient function.…Two, it returns the robot itself at…the end of the verifications…so we can chain the calls together in a fluid manner.…
First create the base class screen robot.…Right click on the test folder…and the Android test Java.…Select "New Java Class"…We will call it screen robot.…This is going to be an abstract class…that contains view related methods.…So in line three put the word abstract after public.…We are going to make it a generic class.…So after the word screen robot…add T extends screen robot.…
The generic type T allows us to write the shared methods…in this base class but still return the proper type…so that we can chain them up in a fluid manner.…This becomes clearer with an actual method.…So let's write one.…Check is hidden.…We are going to write this method…
- 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.