Files

Srujan Gaddam 2407f699e9 Move package:web dependency to dev dependency (#139696 )

Pinning the package:web dependency constrains downstream packages from
using newer versions and making sure they support the version pinned in
Flutter. Since the usage of package:web in Flutter is light, we should
instead have a small shim like the engine and keep package:web as a dev
dependency only.

2023-12-15 08:53:27 -08:00

lib

Remove dead code (#126266 )

2023-05-09 15:47:16 +00:00

test_driver

[web] dispatch corresponding keyup events in text editing integrations (#136874 )

2023-11-03 14:44:14 +01:00

web

[web] use local CanvasKit bundle in all e2e tests (#92305 )

2021-10-26 19:08:05 -07:00

pubspec.yaml

Move package:web dependency to dev dependency (#139696 )

2023-12-15 08:53:27 -08:00

README.md

[web] fix web_e2e_tests README (#92277 )

2021-10-21 17:58:07 -07:00

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