BaseIntegrationTest class abstract

Properties

binding IntegrationTestHelperBinding
final
hashCode int
The hash code for this object.
no setterinherited
runtimeType Type
A representation of the runtime type of the object.
no setterinherited
tester WidgetTester
getter/setter pair

Methods

changeSliderForKey(String fieldKey, {required double percentage}) Future<void>
changeSliderForTooltip(String toolTip, {required double percentage}) Future<void>
changeSliderForType({required double percentage}) Future<void>
dismissBottomSheet() Future<void>
dismissModal() Future<void>
enterText(String fieldKey, String inputText) Future<void>
initializeTests(WidgetTester tester, Widget main, {int waitForMilliseconds = 850}) Future<void>
isPlatformAndroid() Future<bool>
loadFixtureJSON(String fixturePath) Future
noSuchMethod(Invocation invocation) → dynamic
Invoked when a nonexistent method or property is accessed.
inherited
scrollPicker(Finder widgetFinder, String pickerElement) Future<void>
scrollToListItemText(String listKey, String itemText) Future<void>
selectPlatformDate(DateTime startingDate, DateTime endingDate) Future<void>
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.
setupInitialData() Future<void>
setWaitMilliseconds(int waitForMilliseconds) → void
takeScreenshot(String filePath) Future<void>
tapBackArrow() Future<void>
tapCloseButton() Future<void>
tapDeleteKey() Future<void>
tapDoneButton() Future<void>
tapEnterKey() Future<void>
tapForIcon(IconData widgetIcon) Future<void>
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.
tapForIconTooltip(String widgetTooltip) Future<void>
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.
tapForKey(String fieldKey) Future<void>
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.
tapForTooltip(String toolTip) Future<void>
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.
tapForType(Type fieldType) Future<void>
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.
tapListItem({required String widgetPrefix, required int itemIndex}) Future<void>
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.
tapListWidget(int itemIndex, {required String widgetPrefix, required String widgetType}) Future<void>
tapSearchKey() Future<void>
tapShiftKey() Future<void>
tapSpaceKey() Future<void>
tapWidget(String widgetText) Future<void>
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.
toString() String
A string representation of this object.
inherited
verifyExactText(String itemText, {bool shouldThrowError = true}) Future<bool>
verifyListExactText(int itemIndex, {required String widgetPrefix, required String widgetSuffix, required String expectedText}) Future<void>
verifyTextFieldForKey(String fieldKey, String itemText) Future<void>
verifyTextForKey(String fieldKey, String itemText, {bool shouldThrowError = true}) Future<bool>
waitForUI({int durationMultiple = 1}) Future<void>

Operators

operator ==(Object other) bool
The equality operator.
inherited