We can see that our test pass successfully in the CI, and use the emulator provided by reactivecircus.
Update GitHub actions to use hashes instead of. We just have to push the file into the repository and the workflow will be triggered:Īnd if you click on the workflow you should see something like this:Īnd if you click on "Summary" you should see your artifact (screenshots): Require at least Dart > 2.17.0 Add the list and readme commands. The most important in this workflow is the job "Run Flutter Driver tests", the action will start an emulator for us then execute the script provided and here we use the same command as before in local.Īnd finally, we upload the screenshots in artifact so we can check it later. OnScreenshot: (String screenshotName, List screenshotBytes) async screenshots/ test-integration.yaml Import 'package:integration_test/integration_test_driver_extended.dart' Then we create the test: cd integration_testing_with_ciįirst, we will create the integration_test.dart inside test_driver/ : import 'dart:io' Click on setup a workflow yourself, and it will create a predefined. Create a new workflow: You’ll see many pre-designed workflows for various services, right from AWS to Kubernetes, depending on the type of repository you are on. To do this, we first need to run the flutter build apk command to our already defined suposito flutter action - name: Install Flutter uses: subosito/flutter-actionv2 with: flutter-version: '2.10.0' channel: 'stable' - run: flutter build apk.
SUBOSITO FLUTTER ACTION V1 HOW TO
We will see in this article how to make our first integration test and use Github Action to perform the test in a workflow.īefore we deep dive into the CI workflow we need a simple integration test, to do so we will create a simple application with a test inside it: flutter create integration_testing_with_ci To add workflow to your existing Flutter repository, simply choose Actions.
And more importantly, use a CI to automatically run the tests. During the development of a project, we need something to make integration testing.
0 kommentar(er)
