Running Flutter Integration Tests in AWS Device Farm, Saucelabs, Firebase Test Lab etc
How do I run flutter integration tests (flutter_driver) non locally within an infrastructure like AWS Device Farm, Saucelabs, Firebase Test Lab?
Running flutter_driver tests on my local machine works smoothly and easily however cloud based mobile testing services don't have the required dependencies installed to utilize Flutter CLI commands.
There are a few places in the Flutter repo that indicate this is possible, however I'm having a hard time finding exactly what needs to happen to make this possible (I have limited experience with Android & iOS integration testing).
A few references I've found:
A comment discussing an integration test in the flutter_gallery: https://github.com/flutter/flutter/issues/18879#issuecomment-400816050
A github issue to add a Firebase Test Lab integration test: https://github.com/flutter/flutter/issues/11718
What do I need to add to my flutter app to allow for remote integration testing inside AWS Device Farm, Saucelabs, Firebase Test Lab etc?
Thanks for your help.
flutter flutter-test
add a comment |
How do I run flutter integration tests (flutter_driver) non locally within an infrastructure like AWS Device Farm, Saucelabs, Firebase Test Lab?
Running flutter_driver tests on my local machine works smoothly and easily however cloud based mobile testing services don't have the required dependencies installed to utilize Flutter CLI commands.
There are a few places in the Flutter repo that indicate this is possible, however I'm having a hard time finding exactly what needs to happen to make this possible (I have limited experience with Android & iOS integration testing).
A few references I've found:
A comment discussing an integration test in the flutter_gallery: https://github.com/flutter/flutter/issues/18879#issuecomment-400816050
A github issue to add a Firebase Test Lab integration test: https://github.com/flutter/flutter/issues/11718
What do I need to add to my flutter app to allow for remote integration testing inside AWS Device Farm, Saucelabs, Firebase Test Lab etc?
Thanks for your help.
flutter flutter-test
1
Did you see this flutter.io/docs/testing#continuous-integration-and-testing?
– stt106
Nov 14 '18 at 21:24
add a comment |
How do I run flutter integration tests (flutter_driver) non locally within an infrastructure like AWS Device Farm, Saucelabs, Firebase Test Lab?
Running flutter_driver tests on my local machine works smoothly and easily however cloud based mobile testing services don't have the required dependencies installed to utilize Flutter CLI commands.
There are a few places in the Flutter repo that indicate this is possible, however I'm having a hard time finding exactly what needs to happen to make this possible (I have limited experience with Android & iOS integration testing).
A few references I've found:
A comment discussing an integration test in the flutter_gallery: https://github.com/flutter/flutter/issues/18879#issuecomment-400816050
A github issue to add a Firebase Test Lab integration test: https://github.com/flutter/flutter/issues/11718
What do I need to add to my flutter app to allow for remote integration testing inside AWS Device Farm, Saucelabs, Firebase Test Lab etc?
Thanks for your help.
flutter flutter-test
How do I run flutter integration tests (flutter_driver) non locally within an infrastructure like AWS Device Farm, Saucelabs, Firebase Test Lab?
Running flutter_driver tests on my local machine works smoothly and easily however cloud based mobile testing services don't have the required dependencies installed to utilize Flutter CLI commands.
There are a few places in the Flutter repo that indicate this is possible, however I'm having a hard time finding exactly what needs to happen to make this possible (I have limited experience with Android & iOS integration testing).
A few references I've found:
A comment discussing an integration test in the flutter_gallery: https://github.com/flutter/flutter/issues/18879#issuecomment-400816050
A github issue to add a Firebase Test Lab integration test: https://github.com/flutter/flutter/issues/11718
What do I need to add to my flutter app to allow for remote integration testing inside AWS Device Farm, Saucelabs, Firebase Test Lab etc?
Thanks for your help.
flutter flutter-test
flutter flutter-test
edited Dec 18 '18 at 5:01
mmccabe
1,1101016
1,1101016
asked Nov 14 '18 at 19:38
DanielDaniel
162
162
1
Did you see this flutter.io/docs/testing#continuous-integration-and-testing?
– stt106
Nov 14 '18 at 21:24
add a comment |
1
Did you see this flutter.io/docs/testing#continuous-integration-and-testing?
– stt106
Nov 14 '18 at 21:24
1
1
Did you see this flutter.io/docs/testing#continuous-integration-and-testing?
– stt106
Nov 14 '18 at 21:24
Did you see this flutter.io/docs/testing#continuous-integration-and-testing?
– stt106
Nov 14 '18 at 21:24
add a comment |
2 Answers
2
active
oldest
votes
Although we don't officially support the Flutter framework and Flutter tests on AWS Device Farm, we do have a way for you to run these tests using our "custom environment mode" and by pre-selecting a different, supported framework. My advice would be to do the following:
- I have a very minimal dummy test for Appium Python, a supported test framework located at https://s3-us-west-2.amazonaws.com/aws-devicefarm-support/test_bundle_slim.zip. Download this from there, and, using the command line tool zip, add your local tests to this zip file, with a command such as "zip -r ~/Downloads/test_bundle_slim.zip flutter-tests/"
- Go to AWS Device Farm, setup an automation test run, upload your app, then get to the screen where you select your test type. Choose Appium Python, upload your zip file, and AWS Device Farm will accept the test because of the original dummy Appium Python files we've left in the zip file.
- Select "customize your test environment" below there, and a new window below with a YAML test spec file will appear. Put the following lines in the pre-test section of your test spec in place of the existing code used to start an Appium server:
code
- >-
if [ $DEVICEFARM_DEVICE_PLATFORM_NAME = "Android" ];
then
# Run EC2 setup code here
curl https://storage.googleapis.com/flutter_infra/releases/beta/linux/flutter_linux_v0.11.3-beta.tar.xz -o flutter_linux_v0.11.3-beta.tar.xz
tar xf flutter_linux_v0.11.3-beta.tar.xz
fi
if [ $DEVICEFARM_DEVICE_PLATFORM_NAME = "iOS" ];
then
# Run Mac setup code here
curl https://storage.googleapis.com/flutter_infra/releases/beta/macos/flutter_macos_v0.11.3-beta.zip -o flutter_macos_v0.11.3-beta.zip
unzip -qq flutter_macos_v0.11.3-beta.zip
fi
- mv flutter ~/flutter
- echo "export PATH=$PATH:$HOME/flutter/bin">> ~/.bash_profile
- export PATH=$PATH:$HOME/flutter/bin
- flutter devices
code
- Likewise, go to the test section of the test spec file and remove the python test command "bin/py.test" and replace it with your Flutter test command, such as "flutter drive --target=./flutter-tests/main.dart
- Save and close this test spec file, and finish setting up the automation run by selecting your devices and setting up their state.
Good luck testing on AWS Device Farm! I have confirmed that these steps do work to setup Flutter properly on our testing platform.
Anurag Goyal, Flutter integration tests require the standard adb shipped with the Android SDK. Device Farm over-writes the standard adb with a custom adb from Amazon which disables port forwarding, a feature required for flutter testing. AFAIK, the only way to get flutter integration tests to run is to use a private Device Farm which is much more expensive than the shared Device Farm. Is this correct?
– mmccabe
Dec 15 '18 at 9:04
Disregard last message. I was able to get a flutter integration test running on the shared Device Farm for android
– mmccabe
Dec 16 '18 at 0:54
Have you tried testing with iOS? I am not having any luck so far... Is there support available from AWS Device Farm?
– mmccabe
Feb 20 at 7:30
add a comment |
Note: this addresses the assumptions that lead to your question. Not a direct answer to your question.
It is possible to run Flutter integration tests on the cloud using emulators only (no actual devices). The following article describes how to set it up. The article includes a working example on Travis-CI.
Flutter unit, widget and integration testing with IOS and Android emulators on Travis-CI
Source code on GitHub, with a link to the latest build, including integration test results running on both iOS and Android, can be found here. Feel free to clone and use as a starting point for your own project.
Running integration tests on actual devices is probably something you want to do if you are building a complex app with wide distribution (a lot of users), etc...
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53307617%2frunning-flutter-integration-tests-in-aws-device-farm-saucelabs-firebase-test-l%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Although we don't officially support the Flutter framework and Flutter tests on AWS Device Farm, we do have a way for you to run these tests using our "custom environment mode" and by pre-selecting a different, supported framework. My advice would be to do the following:
- I have a very minimal dummy test for Appium Python, a supported test framework located at https://s3-us-west-2.amazonaws.com/aws-devicefarm-support/test_bundle_slim.zip. Download this from there, and, using the command line tool zip, add your local tests to this zip file, with a command such as "zip -r ~/Downloads/test_bundle_slim.zip flutter-tests/"
- Go to AWS Device Farm, setup an automation test run, upload your app, then get to the screen where you select your test type. Choose Appium Python, upload your zip file, and AWS Device Farm will accept the test because of the original dummy Appium Python files we've left in the zip file.
- Select "customize your test environment" below there, and a new window below with a YAML test spec file will appear. Put the following lines in the pre-test section of your test spec in place of the existing code used to start an Appium server:
code
- >-
if [ $DEVICEFARM_DEVICE_PLATFORM_NAME = "Android" ];
then
# Run EC2 setup code here
curl https://storage.googleapis.com/flutter_infra/releases/beta/linux/flutter_linux_v0.11.3-beta.tar.xz -o flutter_linux_v0.11.3-beta.tar.xz
tar xf flutter_linux_v0.11.3-beta.tar.xz
fi
if [ $DEVICEFARM_DEVICE_PLATFORM_NAME = "iOS" ];
then
# Run Mac setup code here
curl https://storage.googleapis.com/flutter_infra/releases/beta/macos/flutter_macos_v0.11.3-beta.zip -o flutter_macos_v0.11.3-beta.zip
unzip -qq flutter_macos_v0.11.3-beta.zip
fi
- mv flutter ~/flutter
- echo "export PATH=$PATH:$HOME/flutter/bin">> ~/.bash_profile
- export PATH=$PATH:$HOME/flutter/bin
- flutter devices
code
- Likewise, go to the test section of the test spec file and remove the python test command "bin/py.test" and replace it with your Flutter test command, such as "flutter drive --target=./flutter-tests/main.dart
- Save and close this test spec file, and finish setting up the automation run by selecting your devices and setting up their state.
Good luck testing on AWS Device Farm! I have confirmed that these steps do work to setup Flutter properly on our testing platform.
Anurag Goyal, Flutter integration tests require the standard adb shipped with the Android SDK. Device Farm over-writes the standard adb with a custom adb from Amazon which disables port forwarding, a feature required for flutter testing. AFAIK, the only way to get flutter integration tests to run is to use a private Device Farm which is much more expensive than the shared Device Farm. Is this correct?
– mmccabe
Dec 15 '18 at 9:04
Disregard last message. I was able to get a flutter integration test running on the shared Device Farm for android
– mmccabe
Dec 16 '18 at 0:54
Have you tried testing with iOS? I am not having any luck so far... Is there support available from AWS Device Farm?
– mmccabe
Feb 20 at 7:30
add a comment |
Although we don't officially support the Flutter framework and Flutter tests on AWS Device Farm, we do have a way for you to run these tests using our "custom environment mode" and by pre-selecting a different, supported framework. My advice would be to do the following:
- I have a very minimal dummy test for Appium Python, a supported test framework located at https://s3-us-west-2.amazonaws.com/aws-devicefarm-support/test_bundle_slim.zip. Download this from there, and, using the command line tool zip, add your local tests to this zip file, with a command such as "zip -r ~/Downloads/test_bundle_slim.zip flutter-tests/"
- Go to AWS Device Farm, setup an automation test run, upload your app, then get to the screen where you select your test type. Choose Appium Python, upload your zip file, and AWS Device Farm will accept the test because of the original dummy Appium Python files we've left in the zip file.
- Select "customize your test environment" below there, and a new window below with a YAML test spec file will appear. Put the following lines in the pre-test section of your test spec in place of the existing code used to start an Appium server:
code
- >-
if [ $DEVICEFARM_DEVICE_PLATFORM_NAME = "Android" ];
then
# Run EC2 setup code here
curl https://storage.googleapis.com/flutter_infra/releases/beta/linux/flutter_linux_v0.11.3-beta.tar.xz -o flutter_linux_v0.11.3-beta.tar.xz
tar xf flutter_linux_v0.11.3-beta.tar.xz
fi
if [ $DEVICEFARM_DEVICE_PLATFORM_NAME = "iOS" ];
then
# Run Mac setup code here
curl https://storage.googleapis.com/flutter_infra/releases/beta/macos/flutter_macos_v0.11.3-beta.zip -o flutter_macos_v0.11.3-beta.zip
unzip -qq flutter_macos_v0.11.3-beta.zip
fi
- mv flutter ~/flutter
- echo "export PATH=$PATH:$HOME/flutter/bin">> ~/.bash_profile
- export PATH=$PATH:$HOME/flutter/bin
- flutter devices
code
- Likewise, go to the test section of the test spec file and remove the python test command "bin/py.test" and replace it with your Flutter test command, such as "flutter drive --target=./flutter-tests/main.dart
- Save and close this test spec file, and finish setting up the automation run by selecting your devices and setting up their state.
Good luck testing on AWS Device Farm! I have confirmed that these steps do work to setup Flutter properly on our testing platform.
Anurag Goyal, Flutter integration tests require the standard adb shipped with the Android SDK. Device Farm over-writes the standard adb with a custom adb from Amazon which disables port forwarding, a feature required for flutter testing. AFAIK, the only way to get flutter integration tests to run is to use a private Device Farm which is much more expensive than the shared Device Farm. Is this correct?
– mmccabe
Dec 15 '18 at 9:04
Disregard last message. I was able to get a flutter integration test running on the shared Device Farm for android
– mmccabe
Dec 16 '18 at 0:54
Have you tried testing with iOS? I am not having any luck so far... Is there support available from AWS Device Farm?
– mmccabe
Feb 20 at 7:30
add a comment |
Although we don't officially support the Flutter framework and Flutter tests on AWS Device Farm, we do have a way for you to run these tests using our "custom environment mode" and by pre-selecting a different, supported framework. My advice would be to do the following:
- I have a very minimal dummy test for Appium Python, a supported test framework located at https://s3-us-west-2.amazonaws.com/aws-devicefarm-support/test_bundle_slim.zip. Download this from there, and, using the command line tool zip, add your local tests to this zip file, with a command such as "zip -r ~/Downloads/test_bundle_slim.zip flutter-tests/"
- Go to AWS Device Farm, setup an automation test run, upload your app, then get to the screen where you select your test type. Choose Appium Python, upload your zip file, and AWS Device Farm will accept the test because of the original dummy Appium Python files we've left in the zip file.
- Select "customize your test environment" below there, and a new window below with a YAML test spec file will appear. Put the following lines in the pre-test section of your test spec in place of the existing code used to start an Appium server:
code
- >-
if [ $DEVICEFARM_DEVICE_PLATFORM_NAME = "Android" ];
then
# Run EC2 setup code here
curl https://storage.googleapis.com/flutter_infra/releases/beta/linux/flutter_linux_v0.11.3-beta.tar.xz -o flutter_linux_v0.11.3-beta.tar.xz
tar xf flutter_linux_v0.11.3-beta.tar.xz
fi
if [ $DEVICEFARM_DEVICE_PLATFORM_NAME = "iOS" ];
then
# Run Mac setup code here
curl https://storage.googleapis.com/flutter_infra/releases/beta/macos/flutter_macos_v0.11.3-beta.zip -o flutter_macos_v0.11.3-beta.zip
unzip -qq flutter_macos_v0.11.3-beta.zip
fi
- mv flutter ~/flutter
- echo "export PATH=$PATH:$HOME/flutter/bin">> ~/.bash_profile
- export PATH=$PATH:$HOME/flutter/bin
- flutter devices
code
- Likewise, go to the test section of the test spec file and remove the python test command "bin/py.test" and replace it with your Flutter test command, such as "flutter drive --target=./flutter-tests/main.dart
- Save and close this test spec file, and finish setting up the automation run by selecting your devices and setting up their state.
Good luck testing on AWS Device Farm! I have confirmed that these steps do work to setup Flutter properly on our testing platform.
Although we don't officially support the Flutter framework and Flutter tests on AWS Device Farm, we do have a way for you to run these tests using our "custom environment mode" and by pre-selecting a different, supported framework. My advice would be to do the following:
- I have a very minimal dummy test for Appium Python, a supported test framework located at https://s3-us-west-2.amazonaws.com/aws-devicefarm-support/test_bundle_slim.zip. Download this from there, and, using the command line tool zip, add your local tests to this zip file, with a command such as "zip -r ~/Downloads/test_bundle_slim.zip flutter-tests/"
- Go to AWS Device Farm, setup an automation test run, upload your app, then get to the screen where you select your test type. Choose Appium Python, upload your zip file, and AWS Device Farm will accept the test because of the original dummy Appium Python files we've left in the zip file.
- Select "customize your test environment" below there, and a new window below with a YAML test spec file will appear. Put the following lines in the pre-test section of your test spec in place of the existing code used to start an Appium server:
code
- >-
if [ $DEVICEFARM_DEVICE_PLATFORM_NAME = "Android" ];
then
# Run EC2 setup code here
curl https://storage.googleapis.com/flutter_infra/releases/beta/linux/flutter_linux_v0.11.3-beta.tar.xz -o flutter_linux_v0.11.3-beta.tar.xz
tar xf flutter_linux_v0.11.3-beta.tar.xz
fi
if [ $DEVICEFARM_DEVICE_PLATFORM_NAME = "iOS" ];
then
# Run Mac setup code here
curl https://storage.googleapis.com/flutter_infra/releases/beta/macos/flutter_macos_v0.11.3-beta.zip -o flutter_macos_v0.11.3-beta.zip
unzip -qq flutter_macos_v0.11.3-beta.zip
fi
- mv flutter ~/flutter
- echo "export PATH=$PATH:$HOME/flutter/bin">> ~/.bash_profile
- export PATH=$PATH:$HOME/flutter/bin
- flutter devices
code
- Likewise, go to the test section of the test spec file and remove the python test command "bin/py.test" and replace it with your Flutter test command, such as "flutter drive --target=./flutter-tests/main.dart
- Save and close this test spec file, and finish setting up the automation run by selecting your devices and setting up their state.
Good luck testing on AWS Device Farm! I have confirmed that these steps do work to setup Flutter properly on our testing platform.
answered Nov 15 '18 at 21:40
Anurag GoyalAnurag Goyal
1561
1561
Anurag Goyal, Flutter integration tests require the standard adb shipped with the Android SDK. Device Farm over-writes the standard adb with a custom adb from Amazon which disables port forwarding, a feature required for flutter testing. AFAIK, the only way to get flutter integration tests to run is to use a private Device Farm which is much more expensive than the shared Device Farm. Is this correct?
– mmccabe
Dec 15 '18 at 9:04
Disregard last message. I was able to get a flutter integration test running on the shared Device Farm for android
– mmccabe
Dec 16 '18 at 0:54
Have you tried testing with iOS? I am not having any luck so far... Is there support available from AWS Device Farm?
– mmccabe
Feb 20 at 7:30
add a comment |
Anurag Goyal, Flutter integration tests require the standard adb shipped with the Android SDK. Device Farm over-writes the standard adb with a custom adb from Amazon which disables port forwarding, a feature required for flutter testing. AFAIK, the only way to get flutter integration tests to run is to use a private Device Farm which is much more expensive than the shared Device Farm. Is this correct?
– mmccabe
Dec 15 '18 at 9:04
Disregard last message. I was able to get a flutter integration test running on the shared Device Farm for android
– mmccabe
Dec 16 '18 at 0:54
Have you tried testing with iOS? I am not having any luck so far... Is there support available from AWS Device Farm?
– mmccabe
Feb 20 at 7:30
Anurag Goyal, Flutter integration tests require the standard adb shipped with the Android SDK. Device Farm over-writes the standard adb with a custom adb from Amazon which disables port forwarding, a feature required for flutter testing. AFAIK, the only way to get flutter integration tests to run is to use a private Device Farm which is much more expensive than the shared Device Farm. Is this correct?
– mmccabe
Dec 15 '18 at 9:04
Anurag Goyal, Flutter integration tests require the standard adb shipped with the Android SDK. Device Farm over-writes the standard adb with a custom adb from Amazon which disables port forwarding, a feature required for flutter testing. AFAIK, the only way to get flutter integration tests to run is to use a private Device Farm which is much more expensive than the shared Device Farm. Is this correct?
– mmccabe
Dec 15 '18 at 9:04
Disregard last message. I was able to get a flutter integration test running on the shared Device Farm for android
– mmccabe
Dec 16 '18 at 0:54
Disregard last message. I was able to get a flutter integration test running on the shared Device Farm for android
– mmccabe
Dec 16 '18 at 0:54
Have you tried testing with iOS? I am not having any luck so far... Is there support available from AWS Device Farm?
– mmccabe
Feb 20 at 7:30
Have you tried testing with iOS? I am not having any luck so far... Is there support available from AWS Device Farm?
– mmccabe
Feb 20 at 7:30
add a comment |
Note: this addresses the assumptions that lead to your question. Not a direct answer to your question.
It is possible to run Flutter integration tests on the cloud using emulators only (no actual devices). The following article describes how to set it up. The article includes a working example on Travis-CI.
Flutter unit, widget and integration testing with IOS and Android emulators on Travis-CI
Source code on GitHub, with a link to the latest build, including integration test results running on both iOS and Android, can be found here. Feel free to clone and use as a starting point for your own project.
Running integration tests on actual devices is probably something you want to do if you are building a complex app with wide distribution (a lot of users), etc...
add a comment |
Note: this addresses the assumptions that lead to your question. Not a direct answer to your question.
It is possible to run Flutter integration tests on the cloud using emulators only (no actual devices). The following article describes how to set it up. The article includes a working example on Travis-CI.
Flutter unit, widget and integration testing with IOS and Android emulators on Travis-CI
Source code on GitHub, with a link to the latest build, including integration test results running on both iOS and Android, can be found here. Feel free to clone and use as a starting point for your own project.
Running integration tests on actual devices is probably something you want to do if you are building a complex app with wide distribution (a lot of users), etc...
add a comment |
Note: this addresses the assumptions that lead to your question. Not a direct answer to your question.
It is possible to run Flutter integration tests on the cloud using emulators only (no actual devices). The following article describes how to set it up. The article includes a working example on Travis-CI.
Flutter unit, widget and integration testing with IOS and Android emulators on Travis-CI
Source code on GitHub, with a link to the latest build, including integration test results running on both iOS and Android, can be found here. Feel free to clone and use as a starting point for your own project.
Running integration tests on actual devices is probably something you want to do if you are building a complex app with wide distribution (a lot of users), etc...
Note: this addresses the assumptions that lead to your question. Not a direct answer to your question.
It is possible to run Flutter integration tests on the cloud using emulators only (no actual devices). The following article describes how to set it up. The article includes a working example on Travis-CI.
Flutter unit, widget and integration testing with IOS and Android emulators on Travis-CI
Source code on GitHub, with a link to the latest build, including integration test results running on both iOS and Android, can be found here. Feel free to clone and use as a starting point for your own project.
Running integration tests on actual devices is probably something you want to do if you are building a complex app with wide distribution (a lot of users), etc...
answered Dec 10 '18 at 4:54
mmccabemmccabe
1,1101016
1,1101016
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53307617%2frunning-flutter-integration-tests-in-aws-device-farm-saucelabs-firebase-test-l%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Did you see this flutter.io/docs/testing#continuous-integration-and-testing?
– stt106
Nov 14 '18 at 21:24