Start of main content

Cross-platform Flutter native autotests

Day 2


Maria will start her story by getting to know Flutter and autotests on it. There will be short information about the types of tests on Flutter, who writes them in Surf and how, and most importantly - why it is so. We will also touch on the strategy: why these types of autotests are needed and what tools will be a good addition.

When Surf started to get acquainted with autotests on Flutter, there was no integration_test package yet, which allows working with widget and E2E tests almost simultaneously. Therefore, the company began to look for opportunities to make life easier for themselves when writing these types of tests.

The team conventionally merged the widget and E2E, adding an abstraction layer to use one call to two types of tests. They also took reusable components that helped in the implementation of both E2E and widget tests. And also connected gherkin using the flutter_gherkin framework.

After Flutter expanded its testing capabilities, provided access to easy work with E2E and widgets using the integration_test package, Surf switched to it. But they continue to use reusable components and gherkin.

At the end of the talk, Maria will tell you what the team learned and how they built the test structure. We will also touch on the features that Surf managed to notice during the work with autotesting on Flutter.

  • #dart
  • #integration-tests
  • #widget-tests
  • #flutter
  • #calabash


Invited experts