Both methods are respectively executed before and after the test us run. Next, we have the methods setUpAll and tearDownAll. The button finder, on the other hand, uses byType since there is only a single FloatingActionButton in our app. This is necessary since our sample app contains more than one Text widget. Notice for the textFinder method, byValueKey is used to locate our text instance. We create two finders for locating and referencing the widgets we will be interacting with this test. Let’s breakdown the functions in our file. The snippet about is a snippet driver file for incrementing the app counter. 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. Our app.dart file contains an instrumented version of our app. Two files are necessary since unlike other tests, Flutter integration tests are executed in different processes. In our driver folder, two files need to be created, app.dart and app_test.dart. To get started, we need to create the directory test_driver folder in our project root. Integrating screenshots is a very easy process. Note: In the example above, we use the absolute path of the export folder, you can use Codemagic’s environment variable if you desire. 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. devices - Controls the list of frames and platforms to capture screenshots.staging - Temporary location for storing captured screenshots.
test_driver/app.dart staging: /Users/builder/exported_artefacts devices:Īt first glance, you might be a little confused but fear not:
0 kommentar(er)
