mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
![]() * Adds support for `flutter test --wasm`. * The test compilation flow is a bit different now, so that it supports compilers other than DDC. Specifically, when we run a set of unit tests, we generate a "switchboard" main function that imports each unit test and runs the main function for a specific one based off of a value set by the JS bootstrapping code. This way, there is one compile step and the same compile output is invoked for each unit test file. * Also, removes all references to `dart:html` from flutter/flutter. * Adds CI steps for running the framework unit tests with dart2wasm+skwasm * These steps are marked as `bringup: true`, so we don't know what kind of failures they will result in. Any failures they have will not block the tree at all yet while we're still in `bringup: true`. Once this PR is merged, I plan on looking at any failures and either fixing them or disabling them so we can get these CI steps running on presubmit. This fixes https://github.com/flutter/flutter/issues/126692 |
||
---|---|---|
.. | ||
abstract_method_smoke_test | ||
android_custom_host_app | ||
android_embedding_v2_smoke_test | ||
android_host_app/.gradle | ||
android_host_app_v2_embedding | ||
android_module_host_with_custom_build_v2_embedding/app/src/main/java/io/flutter/addtoapp | ||
android_semantics_testing | ||
android_verified_input | ||
android_views | ||
channels | ||
deferred_components_test | ||
external_textures | ||
flavors | ||
flutter_gallery | ||
gradle_deprecated_settings | ||
hybrid_android_views | ||
ios_add2app_life_cycle | ||
ios_app_with_extensions | ||
ios_host_app | ||
ios_host_app_swift | ||
ios_platform_view_tests | ||
module_host_with_custom_build/.gradle | ||
module_host_with_custom_build_v2_embedding | ||
new_gallery | ||
non_nullable | ||
platform_interaction | ||
release_smoke_test | ||
spell_check | ||
ui | ||
web | ||
web_compile_tests | ||
web_e2e_tests | ||
wide_gamut_test | ||
windows_startup_test | ||
README.md |
Automated Flutter integration test suites
Each suite consists of either a complete Flutter app and a flutter_driver
specification that drives tests from the UI, or a native app that is meant to
integrate with Flutter for testing.
Intended for use with devicelab tests.
If you want to run a driver test locally, to debug a problem with a test, you can use this command from the appropriate subdirectory:
flutter drive -t <test> --driver <driver>
For example:
flutter drive -t lib/keyboard_resize.dart --driver test_driver/keyboard_resize_test.dart