I have installed the Dart plugin in Goland. It is possible to run dart tests from the UI
, as you can run go tests from the UI?
Related
I am able to run automation tests on sample flutter application using flutter_driver on Android Emulator. I am looking for options of executing on Device Clouds. There are few threads which talk about executions on AWS Device Farm. However, I am interested in Firebase Test Lab. Similar to how we can execute automated scripts in SauceLabs, is there an option to run automated tests in Firebase Test Lab using flutter_driver?
It's currently not possible. Test Lab only supports testing Android apps with Espresso or UI Automator, and iOS apps with XCTest. There is currently no other framework support. As stated in the documentation:
Test Lab runs Espresso and UI Automator 2.0 tests on Android apps, and XCTest tests on iOS apps. Write tests using one of those frameworks, then run them through the Firebase console or the gcloud command line interface.
Feel free to file a feature request with Firebase support.
Instead of flutter_driver , use integration_test package
Tests written with the integration_test package can:
1- Run directly on the target device, allowing you to test on multiple Android or iOS devices using Firebase Test Lab.
2- Run using flutter_driver.
3- Use flutter_test APIs, making integration tests more like writing widget tests.
You can learn more about Migrating from flutter_driver here .
I am able to run automation tests on sample flutter application using flutter_driver on Android Emulator. I am looking for options of executing on Device Clouds. There are few threads which talk about executions on AWS Device Farm. However, I am interested in Firebase Test Lab. Similar to how we can execute automated scripts in SauceLabs, is there an option to run automated tests in Firebase Test Lab using flutter_driver?
It's currently not possible. Test Lab only supports testing Android apps with Espresso or UI Automator, and iOS apps with XCTest. There is currently no other framework support. As stated in the documentation:
Test Lab runs Espresso and UI Automator 2.0 tests on Android apps, and XCTest tests on iOS apps. Write tests using one of those frameworks, then run them through the Firebase console or the gcloud command line interface.
Feel free to file a feature request with Firebase support.
Instead of flutter_driver , use integration_test package
Tests written with the integration_test package can:
1- Run directly on the target device, allowing you to test on multiple Android or iOS devices using Firebase Test Lab.
2- Run using flutter_driver.
3- Use flutter_test APIs, making integration tests more like writing widget tests.
You can learn more about Migrating from flutter_driver here .
I am developing a cross platform application for Android and iOS and have chosen to use react-native-firebase. I have cloned the project from react-native-firebase free starter kit. When I build my application the first time using "npm run android" it works fine but the second time I get the error:
Execution failed for task ':app:processDebugGoogleServices'.
Failed to delete: C:\\android\app\build\generated\res\google-services\debug
To run the application again in the Android Studio emulator I have to manually delete the build folder and run "npm run android" again so it can create a new one. Why is this happening and how can I solve it?
I have the same problem.
Though, as a workaround, I don't clean the build folder : I start again the build (react-native run-android) and it goes live.
I may have to start several times.
So that means that the problem is about synchronization in the build process.
I've tried to set in my gradle.properties :
org.gradle.parallel=false
org.gradle.workers.max=1
Till now it works fine!
How can one set up qunit to run integration tests against a remote site? I've used ember-cli test runner which has qunit + testem built in to run interation tests locally in an ember-cli project. How it does this, is to load the entire ember app in the qunit container then run the tests which can be unit or integration tests. This approach is also good if I can't have a JRE dependancy.
I think it may be possible to be able to load fooDomain.com/somepath in an iframe and then run the tests against it.
Has anyone a workflow for this?
I am writing e2e Tests for some JS application at the moment. Since I am not a JS developer I was investigating on this theme for a while and ended up with the following setup:
Jasmine2 as testing framework
grunt as "build-tool"
protractor as test runner
jenkins as CI server (already in use for plenty java projects)
Although the application under tests is not written in angular I decided to go for protractor, following a nice guide on howto make protractor run nicely even without angular.
Writing some simple tests and running them locally worked like a charm. In order to implicitly wait for some elements to show up in den DOM I used the following code in my conf.js:
onPrepare: function() {
browser.driver.manage().timeouts().implicitlyWait(5000);
}
All my tests were running as expected and so I decided to go to the next step, i.e. installation in the CI server.
The development team of the aplication I want to tests was already using grunt to build their application so I decided to just hook myself into that. The goal of my new grunt task is to:
assemble the application
start a local webserver running the application
run my protractor test
write some test reports
Finally I accomplished all of the above steps, but I am dealing with a problem now I cannot solve and did not find any help googling it. In order to run the protractor test from grunt I installed the grunt-protractor-runner.
The tests are running, BUT the implicit wait is not working, causing some tests to fail. When I added some explicit waits (browser.sleep(...)) everything is ok again but that is not what I want.
Is there any chance to get implicitly waiting to work when using the grunt-protractor-runner?
UPDATE:
The problem does not have anything to do with the grunt-protractor-runner. When using a different webserver I start up during my taks its working again. To be more precisley: Using the plugin "grunt-contrib-connect" the tests is working using the plugin "grunt-php" the test fails. So I am looking for another php server for grunt now. I will be updating this question.
UPDATE 2:
While looking for some alternatives I considered and finally decided to mock the PHP part of the app.