Merge Patrol and PatrolTester

[bartekpacia]

Introduction

Currently, a different object is used to interact with the OS (Patrol), and a different to interact with Flutter PatrolTester.

We'd like to embed Patrol (and rename it to NativeAutomator or something like this) in PatrolTester. At the same time, we don't want to force our users to use patrolTest instead of testWidgets, so we want to keep the current method of initializing Patrol.

Scope

Add a native bool flag to maestroTest which, if true, will initialize PatrolTester.native:

Currently:

"the old way" (but by no means deprecated – we want to let users use only the native automator, without having to use patrolTest().

void main() {
  final patrol = Patrol.forTest();

  patrolTest(
    'taps around',
    config: patrolConfig,
    ($) async {
      await patrol.openQuickSettings();
      await patrol.pressBack();

      await $('Something').tap();
    },
  );
}

We're aiming for:

"the new way"

void main() {
  patrolTest(
    'taps around',
    config: patrolConfig,
    native: true,
    ($) async {
      await $.native.openQuickSettings();
      await $.native.pressBack();

      await $('Something').tap();
    },
  );
}

To do

• Embed Patrol class inside of PatrolTester and rename it #296
• Update example app's integration tests to use $.native instead of a separate object #298
• Update documentation to use $.native #299

[bartekpacia]

cc @mateuszwojtczak @jakubfijalkowski - just please say what you think

[bartekpacia]

This has been done.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar problem, please file a new issue. Make sure to follow the template and provide all the information necessary to reproduce the issue.