patrol test: Uninstalling the app after the test was run

[bartekpacia]

To uninstall an app, we need to know its package name / bundle ID.

The easiest way to accomplish this is to ask the user to specify these values in pubspec.yaml:

Example

# pubspec.yaml

dependencies:
  bloc: ^7.2.0
  # ...

dev_dependencies:
  patrol: ^1.0.0
  # ...

patrol:
  android_app_id: pl.leancode.patrol.example
  ios_app_id: pl.leancode.patrol.Example
  # macos, windows in the future?

or:

patrol:
  app_ids:
    android: pl.leancode.patrol.example
    ios: pl.leancode.patrol.Example
    # more in the future?

cc @mateuszwojtczak

[bartekpacia]

patrol:
  android:
    package_name: pl.leancode.patrol.example
    app_name: "Patrol example"
  ios:
    bundle_id: pl.leancode.patrol.Example
    app_name: "Patrol example"

Adding app name will unblock #157

[bartekpacia]

Do we also want to uninstall the app if it is already present on the device?

[bartekpacia]

Reopening because pubspec.yaml fields are not implemented yet.

[crisboarna]

Hi, I am looking at using your testing framework. This issue solution seems to not cover the case of flavours ? If you want to run Android flavours tests it will not be a static package name, there will be a suffix added to it. Is that scenario covered ?

[bartekpacia]

Hi @crisboarna, thanks for taking a look at us! :)

If you configured your app to have package_name according to the flavor, you'll be able to specify this. For example, let's say that your package_name is com.crisboarna.calendar and it has 3 flavors: dev, staging, and prod, and that you wish to run your integration tests with staging flavor. Then you'll be able to do:

patrol:
  android:
    package_name: com.crisboarna.calendar.staging
    app_name: Awesome Calendar

To run these tests (with automatic uninstall), you'll execute:

patrol test --flavor staging

Does it solve your use case?

[bartekpacia]

Thinking about it now, it'd also make sense to include flavor and dart-defines in pubspec.yaml:

patrol:
  flavor: staging
  dart-defines:
    CRASHLYTICS_ENABLED: false

  android:
    package_name: com.crisboarna.calendar.staging
    app_name: Awesome Calendar
    dart-defines:
      SOME_KEY: this dart-define will be only present on Android

  ios:
    bundle_id: com.crisboarna.Calendar.staging
    app_name: Awesome Calendar
    dart-defines:
      SOME_KEY: this dart-define will be only present on iOS

[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.