mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
![]() * Add an integration test to plugin template example Dart unit tests don't exercise host-side plugin code at all, so the example tests in the plugin template currently have very little meaningful coverage. This adds an integration test to the example app when creating a plugin, so that there's an example of how to actually test that a complete round-trip plugin call works. This is done as a separate template that's currently only used by the plugin template because I don't know what a good example for a non-plugin case would be that isn't largely just a duplicate of the widget tests. However, the integration test pre-includes conditionals around the parts that are plugin-specific so that it can more easily be expanded to other use cases later (e.g., in https://github.com/flutter/flutter/issues/68818). Part of https://github.com/flutter/flutter/issues/82458 * Add integration test to expected dependencies of a plugin app * Test fixes * Make an explicit test case |
||
---|---|---|
.. | ||
app | ||
app_integration_test/integration_test | ||
app_shared | ||
app_test_widget/test | ||
cocoapods | ||
module | ||
package | ||
plugin | ||
plugin_ffi | ||
plugin_shared | ||
skeleton | ||
README.md | ||
template_manifest.json |
This directory contains templates for flutter create
.
The *_shared
subdirectories provide files for multiple templates.
app_shared
forapp
andskeleton
.plugin_shared
for (method channel)plugin
andplugin_ffi
.
For example, there are two app templates: app
(the counter app)
and skeleton
(the more advanced list view/detail view app).
┌────────────┐
│ app_shared │
└──┬──────┬──┘
│ │
│ │
▼ ▼
┌─────┐ ┌──────────┐
│ app │ │ skeleton │
└─────┘ └──────────┘
Thanks to app_shared
, the templates for app
and skeleton
can contain
only the files that are specific to them alone, and the rest is automatically
kept in sync.