text stringlengths 1 474 |
|---|
One of their jobs is to decide when a package |
has met the quality bar to become a Flutter Favorite.The current committee members |
(ordered alphabetically by last name) |
are as follows:If you’d like to nominate a package or plugin as a |
potential future Flutter Favorite, or would like |
to bring any other issues to the attention of the committee, |
send the committee an email.<topic_end> |
<topic_start> |
Flutter Favorite usage guidelines |
Flutter Favorite packages are labeled as such on pub.dev |
by the Flutter team. |
If you own a package that has been designated as a Flutter Favorite, |
you must adhere to the following guidelines:<topic_end> |
<topic_start> |
What’s next |
You should expect the list of Flutter Favorite packages |
to grow and change as the ecosystem continues to thrive. |
The committee will continue working with package authors |
to increase quality, as well as consider other areas of the |
ecosystem that could benefit from the Flutter Favorite program, |
such as tools, consulting firms, and prolific Flutter contributors.As the Flutter ecosystem grows, |
we’ll be looking at expanding the set of metrics, |
which might include the following:<topic_end> |
<topic_start> |
Flutter Favorites |
You can see the complete list of |
Flutter Favorite packages on pub.dev. |
<topic_end> |
<topic_start>Testing Flutter apps |
The more features your app has, the harder it is to test manually. |
Automated tests help ensure that your app performs correctly before |
you publish it, while retaining your feature and bug fix velocity.info Note |
For hands-on practice of testing Flutter apps, see the |
How to test a Flutter app codelab.Automated testing falls into a few categories:Generally speaking, a well-tested app has many unit and widget tests, |
tracked by code coverage, plus enough integration tests |
to cover all the important use cases. This advice is based on |
the fact that there are trade-offs between different kinds of testing, |
seen below.<topic_end> |
<topic_start> |
Unit tests |
A unit test tests a single function, method, or class. |
The goal of a unit test is to verify the correctness of a |
unit of logic under a variety of conditions. |
External dependencies of the unit under test are generally |
mocked out. |
Unit tests generally don’t read from or write |
to disk, render to screen, or receive user actions from |
outside the process running the test. |
For more information regarding unit tests, |
you can view the following recipes |
or run flutter test --help in your terminal.info Note |
If you’re writing unit tests for code that |
uses plugins and you want to avoid crashes, |
check out Plugins in Flutter tests. |
If you want to test your Flutter plugin, |
check out Testing plugins.<topic_end> |
<topic_start>Recipes |
An introduction to unit testingMock dependencies using Mockito<topic_end> |
<topic_start> |
Widget tests |
A widget test (in other UI frameworks referred to as component test) |
tests a single widget. The goal of a widget test is to verify that the |
widget’s UI looks and interacts as expected. Testing a widget involves |
multiple classes and requires a test environment that provides the |
appropriate widget lifecycle context.For example, the Widget being tested should be able to receive and |
respond to user actions and events, perform layout, and instantiate child |
widgets. A widget test is therefore more comprehensive than a unit test. |
However, like a unit test, a widget test’s environment is replaced with |
an implementation much simpler than a full-blown UI system.<topic_end> |
<topic_start>Recipes |
An introduction to widget testingFind widgetsHandle scrollingTap, drag, and enter text<topic_end> |
<topic_start> |
Integration tests |
An integration test tests a complete app or a large part of an app. |
The goal of an integration test is to verify that all the widgets |
and services being tested work together as expected. |
Furthermore, you can use integration |
tests to verify your app’s performance.Generally, an integration test runs on a real device or an OS emulator, |
such as iOS Simulator or Android Emulator. |
The app under test is typically isolated |
from the test driver code to avoid skewing the results.For more information on how to write integration tests, see the integration |
testing page.<topic_end> |
<topic_start>Recipes |
An introduction to integration testingPerformance profiling<topic_end> |
<topic_start> |
Continuous integration services |
Continuous integration (CI) services allow you to run your |
tests automatically when pushing new code changes. |
This provides timely feedback on whether the code |
changes work as expected and do not introduce bugs.For information on running tests on various continuous |
integration services, see the following: |
<topic_end> |
<topic_start>An introduction to unit testing |
How can you ensure that your app continues to work as you |
add more features or change existing functionality? |
By writing tests.Unit tests are handy for verifying the behavior of a single function, |
method, or class. The test package provides the |
core framework for writing unit tests, and the flutter_test |
package provides additional utilities for testing widgets.This recipe demonstrates the core features provided by the test package |
using the following steps:For more information about the test package, |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.