---
title: "Flutter Test | Skills We Assign For | Azendo"
description: "Flutter Test for Dart and widget testing — the three test levels and where golden tests fit, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/flutter-test/"
---

[Skills](https://azendo.co/skills/) QA and delivery tooling 

# Flutter Test.

Flutter Test is the framework bundled with the Flutter SDK, covering unit tests, widget tests that render a widget tree without a device, and integration tests that drive a full application on a device or emulator.

## Where Flutter Test fits on a long engagement.

Widget tests are the level that makes Flutter testing unusually productive. Because the framework renders its own widgets, a widget tree can be built and asserted against in milliseconds with no device involved — genuine interface coverage at roughly unit-test speed, which most platforms cannot offer.

Golden tests extend that to appearance by comparing rendered output against stored images. They catch visual regressions nothing else will, and they need care: goldens differ across platforms and font rendering, so generating them on one machine and asserting on another produces failures that are about the environment rather than the code.

## What an assigned team does with Flutter Test.

The natural balance on a Flutter codebase is heavy widget coverage and a small integration suite. Teams that skip widget tests and rely on integration tests end up with a slow pipeline and poor coverage, which is the worst combination available.

Getting that balance agreed early is a test-strategy decision rather than a tooling one, assigned under [qa outsourcing](https://azendo.co/services/qa-engineering-and-test-automation/) alongside the development capacity.

## What we use Flutter Test for.

* Interface coverage at unit-test speed Widget trees rendered and asserted in milliseconds, with no device in the loop.
* Visual regressions caught automatically Golden tests generated in a controlled environment so failures mean real changes.
* A small, meaningful integration suite Full-application tests limited to journeys that genuinely need a device.

## How Flutter Test capacity is assigned.

Flutter test capacity is assigned with the Flutter development capacity, with the balance between widget and integration coverage agreed at scoping.

## Roles we assign Flutter Test for

* [Flutter Developer Mobile development](https://azendo.co/services/mobile-development/flutter-developer/)

## Service lines it sits in

* [Mobile development](https://azendo.co/services/mobile-development/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in qa and delivery tooling

* [Jira — skill we assign for](https://azendo.co/skills/jira/)
* [TestRail — skill we assign for](https://azendo.co/skills/testrail/)
* [Jest — skill we assign for](https://azendo.co/skills/jest/)
* [React Testing Library — skill we assign for](https://azendo.co/skills/react-testing-library/)
* [XCTest — skill we assign for](https://azendo.co/skills/xctest/)
* [Espresso — skill we assign for](https://azendo.co/skills/espresso/)
* [Detox — skill we assign for](https://azendo.co/skills/detox/)
* [Playwright — skill we assign for](https://azendo.co/skills/playwright/)

## Tell us what your roadmap needs Flutter Test for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)