github/flutter
7
0
Fork 0
mirror of https://github.com/flutter/flutter.git synced 2025-06-03 00:51:18 +00:00
Code Issues Packages Projects Releases Wiki Activity
a49ee534c6
flutter/dev/integration_tests/web_e2e_tests
History
Srujan Gaddam d8ffc7390c
Pin package:web 0.4.0 (#138428) 
This version is needed so that dart:js_interop can move to extension
types. Also adds some code to handle some breaking changes:

- Body -> Response. Body was an IDL interface mixin type we exposed in
dart:html. Going forward, users should either use Request or Response.
- Casts to JSAny. These are temporary until we move package:web types to
extension types. Currently, package:web types can't implement JSObject
as JSObject will move to be an extension type itself.

Co-authored-by: Kevin Moore <kevmoo@users.noreply.github.com>
2023-11-15 15:03:21 -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 Pin package:web 0.4.0 (#138428) 2023-11-15 15:03:21 -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: