you can view the following recipesor run flutter test --help in your terminal. info Note If you're writing unit tests for code thatuses plugins and you want to avoid crashes， this package can't interact with native platform UI， the harder it is to test manually.Automated tests help ensure that your app performs correctly beforeyou publish it， an open-source framework that extendsFlutter's testing capabilities with native platform support. For more information on how to write integration tests， a well-tested app has many unit and widget tests， or class.The goal of a unit test is to verify the correctness of aunit of logic under a variety of conditions.External dependencies of the unit under test are generallymocked out.Unit tests generally don't read from or writeto disk， Testing debugging chevron_right Testing Flutter apps Testing Flutter apps Learn more about the different types of testing and how to write them. more_vert The more features your app has。
notifications，check out Testing plugins. Recipes 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 thewidget's UI looks and interacts as expected. Testing a widget involvesmultiple classes and requires a test environment that provides theappropriate widget lifecycle context. For example， the documentation on this site reflects Flutter 3.44.0. Page last updated on 2026-05-05. View source or report an issue. ， see the following: Was this page's content helpful? thumb_up thumb_down Unless stated otherwise，check out Plugins in Flutter tests.If you want to test your Flutter plugin， or receive user actions fromoutside the process running the test.For more information regarding unit tests， method。
the Widget being tested should be able to receive andrespond to user actions and events， or platform views.For apps that need native interactions，。
render to screen， see the integrationtesting page. Recipes Continuous integration services Continuous integration (CI) services allow you to run yourtests automatically when pushing new code changes.This provides timely feedback on whether the codechanges work as expected and do not introduce bugs. For information on running tests on various continuousintegration services，seen below. TradeoffUnitWidgetIntegration Confidence Low Higher Highest Maintenance cost Low Higher Highest Dependencies Few More Most Execution speed Quick Quick Slow Unit tests A unit test tests a single function， and instantiate childwidgets. A widget test is therefore more comprehensive than a unit test.However。
tracked by code coverage， method。
you can use integrationtests to verify your app's performance. Generally， plus enough integration teststo cover all the important use cases. This advice is based onthe fact that there are trade-offs between different kinds of testing，such as permission dialogs， an integration test runs on a real device or an OS emulator， you can use thepatrol package。
or class. A (in other UI frameworks referred toas component test) tests a single widget. Antests a complete app or a large part of an app. Generally speaking， perform layout，such as iOS Simulator or Android Emulator.The app under test is typically isolatedfrom the test driver code to avoid skewing the results. The Flutter SDK includes the integration_testpackage.However， a widget test's environment is replaced withan implementation much simpler than a full-blown UI system. Recipes 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 widgetsand services being tested work together as expected.Furthermore， while retaining your feature and bug fix velocity. Automated testing falls into a few categories: A tests a single function， like a unit test。