The selectPlatformDate method allows for testing of an Android DatePickerDialog, and an iOS CupertinoDatePicker and
accepts two DateTime objects. The default date that is set on the date picker is the first parameter @startingDate, and
the destination date is the @endingDate. selectPlatformDate handles the waiting for the UI to load, finding the Picker Widget, and then tapping
or scrolling the correct date Widget components. In addition, it also includes List item prefixes, and positions within the list. Using the selectPlatformDate implementation,
it removes at the least 3 lines of code from your integration tests, and allows that functionality to be reused in your
own custom implementation of the BaseIntegrationTest class.
The tapForIcon handles the waiting for the UI to load, finding the Widget, and then tapping the found Widget.
In addition, it also includes a post tap wait for any screen loading needed. Using the tapForIcon implementation,
we remove at the least 3 lines of code from your integration tests, and allow that functionality to be reused in your
own custom implementation of the BaseIntegrationTest class.
The tapForIconTooltip handles the waiting for the UI to load, finding the Widget, and then tapping the found Widget.
In addition, it also includes a post tap wait for any screen loading needed. Using the tapForIconTooltip implementation,
we remove at the least 3 lines of code from your integration tests, and allow that functionality to be reused in your
own custom implementation of the BaseIntegrationTest class.
The tapForKey handles the waiting for the UI to load, finding the Widget, and then tapping the found Widget.
In addition, it also includes a post tap wait for any screen loading needed. Using the tapForKey implementation,
we remove at the least 3 lines of code from your integration tests, and allow that functionality to be reused in your
own custom implementation of the BaseIntegrationTest class.
The tapForTooltip handles the waiting for the UI to load, finding the Widget, and then tapping the found Widget.
In addition, it also includes a post tap wait for any screen loading needed. Using the tapForTooltip implementation,
we remove at the least 3 lines of code from your integration tests, and allow that functionality to be reused in your
own custom implementation of the BaseIntegrationTest class.
The tapForType handles the waiting for the UI to load, finding the Widget, and then tapping the found Widget.
In addition, it also includes a post tap wait for any screen loading needed. Using the tapForType implementation,
we remove at the least 3 lines of code from your integration tests, and allow that functionality to be reused in your
own custom implementation of the BaseIntegrationTest class.
The tapListItem method handles the waiting for the UI to load, finding the Widget, and then tapping the found Widget.
In addition, it also includes List item prefixes, and positions within the list. Using the tapListItem implementation,
it removes at the least 3 lines of code from your integration tests, and allows that functionality to be reused in your
own custom implementation of the BaseIntegrationTest class.
The tapWidget handles the waiting for the UI to load, finding the Widget, and then tapping the found Widget.
In addition, it also includes a post tap wait for any screen loading needed. Using the tapWidget implementation,
we remove at the least 3 lines of code from your integration tests, and allow that functionality to be reused in your
own custom implementation of the BaseIntegrationTest class.