mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
![]() ## Description This introduces a list of packages that we will explicitly not pin. It is to be used for things where the package isn't actually published, but is a transitive dependency of another package included in the SDK. This happens with the `macros` package, for instance, which depends on the private, unpublished, `_macros` package where the SDK does some tricky things to depend on it (it depends on "any", but ships it as part of the SDK). Also ran `flutter update-packages --force-update` to update all of the pubspec files. ## Related Issues - Fixes #147656 ## Tests - Added a test that makes sure that explicitly unpinned packages don't show up in the pinned list. |
||
---|---|---|
.. | ||
lib | ||
test_driver | ||
web | ||
pubspec.yaml | ||
README.md |
Flutter Web integration tests
To run the tests in this package download the chromedriver matching the version of Chrome. To find out the version of your Chrome installation visit chrome://version.
Start chromedriver
using the following command:
chromedriver --port=4444
An integration test is run using the flutter drive
command. Some tests are
written for a specific web renderer and/or specific build mode.
Before running a test, check the _runWebLongRunningTests
function defined in
dev/bots/test.dart, and determine the right web renderer and the build
mode you'd like to run the test in.
Here's an example of running an integration test:
flutter drive --target=test_driver/text_editing_integration.dart \
-d web-server \
--browser-name=chrome \
--profile \
--web-renderer=html
This example runs the test in profile mode (--profile
) using the HTML
renderer (--web-renderer=html
).
More resources:
- chromedriver: https://chromedriver.chromium.org/getting-started
- FlutterDriver: https://github.com/flutter/flutter/wiki/Running-Flutter-Driver-tests-with-Web
package:integration_test
: https://pub.dev/packages/integration_test