Integration Testing Is An AntiPattern

It might seem hyperbole, but integration testing is in fact an antipattern in flutter app development. Let me show you why.

Background On Integration Testing

On such native platforms development frameworks as Android SDK, integrated testing(instrumented testing) cam about as they had no way to test the native views with framework dependencies via just unit testing. And things like Cucumber(Gherkin) BDD testing was hen added on top.

With the Flutter SDK framework, due to part of the SKY-Flutter Engine running during unit testing(it’s why you have to do an ensure binding check on the SKY-Engine, i.e. the call in setup in unit testing) we no longer have the same exact need for using integrated testing.

Now, let me show you why it’s an actual antipattern and that you no longer need integration testing.

Where Is My BDD Testing

Where is the BDD testing if we do not have or use integration testing? Some of you may get my hint already, but let me show the ones who do not get the hint yet. Some testing code: