DEV/flutter_flutter
1
0
Fork 0
mirror of https://github.com/flutter/flutter.git synced 2026-02-04 01:56:32 +08:00
Code Issues Packages Projects Releases Wiki Activity
flutter_flutter/dev/integration_tests/web_e2e_tests
History
Danny Tuppeny cea1d6f055
Unpin DDS and roll pub packages (#147925) 
DDS was temporarily pinned to 4.1.0 because 4.2.0 triggered some test
failures (see https://github.com/flutter/flutter/pull/147250). Those
failures should be fixed by vm_service 14.2.2, so this unpins DDS and
rolls both of these packages (along with devtools_shared, which is a DDS
dependency).

(If the bot updates vm_service before this is done, I can rebase over
that will reduce the size of this PR to just a few files)
2024-05-08 10:35:28 +01:00
..
lib
[web] remove platform_messages_integration test (#147654)
2024-05-01 21:12:01 +00:00
test_driver
[web] remove platform_messages_integration test (#147654)
2024-05-01 21:12:01 +00:00
web
Flutter Web Bootstrapping Improvements (#144434)
2024-03-12 22:41:26 +00:00
pubspec.yaml
Unpin DDS and roll pub packages (#147925)
2024-05-08 10:35:28 +01:00
README.md
Added missing code block language in docs (#147481)
2024-05-01 14:44:27 +00: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: