Test_driver/app.Tripping on LCDThe LCD screen was without a doubt the single feature that made the original G15 such a popular keyboard for Logitech, with countless scores of gamers getting sucked in by the cool idea of having system info and other bits and bobs displayed on a second screen while they gamed. devices - Controls the list of frames and platforms to capture screenshots.staging - Temporary location for storing captured screenshots. archive- Saves screenshots for local use.Devices can be broken up into separate configuration files however we will not be looking at those in this article. Note: In the example above, we use the absolute path of the export folder, you can use Codemagic’s environment variable if you desire.
Integrating screenshots is a very easy process. To get started, we need to create the directory test_driver folder in our project root. In our driver folder, two files need to be created, app.dart and app_test.dart. Two files are necessary since unlike other tests, Flutter integration tests are executed in different processes. Our app.dart file contains an instrumented version of our app. To get started, paste the following code in app.dart:įinal buttonFinder = Type( 'FloatingActionButton') įinal textFinder = ValueKey( 'count-value') Įxpect( await driver.getText(textFinder), "1") In this file, we enable Flutter driver then start the execution of the tests. The snippet about is a snippet driver file for incrementing the app counter. Let’s breakdown the functions in our file. We create two finders for locating and referencing the widgets we will be interacting with this test. Notice for the textFinder method, byValueKey is used to locate our text instance. This is necessary since our sample app contains more than one Text widget.
The button finder, on the other hand, uses byType since there is only a single FloatingActionButton in our app. Next, we have the methods setUpAll and tearDownAll. Both methods are respectively executed before and after the test us run.
0 kommentar(er)
