patrol_cli 1.0.0

patrol_cli: ^1.0.0 copied to clipboard

• Patrol 1.0 is released!)

• patrol test: Improve how external tool invocations are logged when running with --verbose (#906)
• patrol test: Fix .xctrunner app not being uninstalled after tests finish on iOS Simulator (#907)

• Add support for flavor in Patrol configuration block in pubspec.yaml (#892)
• Fix patrol test not propagating PATROL_VERBOSE (activated with --verbose flag) to the Flutter side (#892)

• Fix patrol test broken on Windows when running tests on Android (#889)

• Improve error message of patrol test when the integration_test directory doesn't exist (#876)
• Make patrol test run tests in a more predictable, ls-like order (#882)
• Fix patrol test incorrectly encoding --dart-define when running on Android (#885)
• Display name of currently running test file in top-left corner (#885)

• Enable patrol test for physical iOS devices (#863)

• Make it possible to specify package_name and bundle_id in pubspec.yaml (#868)

  If these values are set, the tool automatically uninstalls the app after every test. It's recommended to set them.

  Example:

  dependencies:
    # ...
  
  dev_dependencies:
    # ...
  
  patrol:
    android:
      package_name: pl.leancode.awesomeapp
      app_name: Awesome App
    ios:
      bundle_id: pl.leancode.AwesomeApp
      app_name: Awesome App
  

• Uninstall app under test after patrol test (#848)

  This currently requires package name (on Android) and bundle identifier (on iOS) to be passed through respective arguments to patrol test. Soon it'll also be possible to define these values in `pubspec.yaml.

• Print helpful links when called without arguments (#865)

• Fix verbose output from Gradle having garbled newlines (#858)

• Add a deprecation warning to patrol drive command (#833)

  Use the new patrol test command. See setup instructions.

• When using patrol test, infer --configuration from --flavor when possible (#796)

• Fix patrol test on Windows (#805)

• Make patrol test more configurable (#791)

• Fix typo in changelog (#783)

• Add patrol test command (#731)

  patrol test runs tests natively (using Gradle on Android and xcodebuild on iOS). This command is hidden from patrol --help for now until we're sure it has the same features patrol drive, but you can already use it. In a future release, patrol drive will be deprecated, and in 1.0, patrol drive will be removed in favor of patrol test.

  Learn more here about why we're deprecating patrol drive.

  Learn more here about how to setup your project to use patrol test.

• Add --label/--no-label flag to patrol drive, that displays the test name over the running app, making it easier to identify which test is currently running (#701)

• Add support for Patrol Next (#646, #671)

• Add support for NativeAutomator.swipe() (#669)

• Add support for --use-application-binary argument for patrol drive (#667)

• Update bootstrap command to generate code working with patrol v0.9.0 (#665)
• Display short name instead of UUID in test results when running on iPhone (#664)

• AutomatorServer:
  • Add 1 second delay after performing permission action on Android (#647)

• Improve output (#644)

• AutomatorServer:
  • Migrate gRPC server from Netty to OkHttp (#642)

• Print status of test runs after patrol drive finishes (#624)

• Print error message when screenshot fails on host side (#625)
• Perform internal refactoring to make testing the CLI easier (#626)

• Fix running tests that failed to build (#615)
• Fix rare crashes on slower machines caused by activity service not running on Android emulator (#615)

• Add support for patrolIntegrationDriver (#593)
• Remove port forwarding, which wasn't needed for some time (#597, #603)

• Fix --dart-defines being malformed (#589)

• Add support for optional .patrol.env file where --dart-defines can be stored to avoid typing them manually in patrol drive invocations (#585)

• Fix crashing on Windows (#586)
• Fix bug with tests running n^2 times instead of n times (#580)

• Fix crashing on Windows (#574)

• Add --repeat argument to patrol drive, which makes flake detection easier (#552)

• Reenable terminal animations (#521)
• Fix infinite wait when more than 2 Android devices are connected (#553)

• Fix patrol doctor crashing on Windows (#546)

• Print more useful info in patrol doctor (#541)
• Accept both device name and device ID for the --device argument to patrol drive (#537)
• Wait for the package service to become active on Android before installing apk (#539, #540)

• Disable terminal animations to fix logs on the CI (#498)

• AutomatorServer:
  • Improve reliability of native interactions on iOS (#489)
  • Set minimum iOS version to 14.0 (#496)

• Fix too aggressive logging when downloading artifacts (#484)

• Make --target flag accept directories (#473)
• Use prebuilt artifacts when running on iOS Simulator (#465)
• Automatically download new artifacts during patrol update (#465)

• Minimize iOS artifact size (#469)

• Prebuild iOS artifacts for iPhones (#454)

• Add version to prebuild iOS artifacts (#460)

• Fix occasional crashes caused by Flutter's version prompt (#456)

• Build iOS artifacts on CI (#452, #452)

In this release, we've focused on stability, reliability, and reducing flakiness.

• AutomatorServer:
  • Add timeouts when interacting with native UI (#437)
  • Implement isPermissionDialogVisible() method (#448)
  • Fix entering text into SecureTextField on iOS (#446)

• Fix trying to run on all attached devices (instead of only the first one) when no device is specified (#442)

• AutomatorServer:
  • Further improve error messages occuring on the native side (#429)

• AutomatorServer:
  • Print more info about errors occuring on the native side (#414)

• AutomatorServer:
  • Fix denyPermission() not working on iOS (#413)

• Improve stability (#397)
• AutomatorServer:
  • Rename getNativeWidgets() to getNativeViews() (#399)
  • Add tapOnNotificationByIndex(), tapOnNotificationBySelector(), and closeHeadsUpNotification() on iOS (#398)

• Fix artifacts being downloaded on every run on Linux and Windows (#392)
• Fix a small typo during patrol drive (#391)
• AutomatorServer:
  • Fix getNativeWidgets() crashing on Android (#393)

• AutomatorServer:
  • Fix handling permission prompts now working in some edge cases (#383)

• Improve update prompt (#377)
• AutomatorServer:
  • Remove remaining Objective-C code (#374)

• AutomatorServer:
  • Implement enabling and disabling cellular on iOS (#371)
  • Fix crash with trying to use non-existent AutomatorServer.xcworkspace when running tests on iOS (#371)

• Build iOS test runner artifact in GitHub Actions (#362)

• Download artifacts from GitHub Releases insted of LeanCode's Azure Storage (#363)

• Release updated AutomatorServers (#338)

• Fix --targets argument to patrol drive (#330)

• Add the targets alias for target option for patrol drive (#314)
• Add the devices alias for device option for patrol drive (#314)
• Add the dart-defines alias for dart-define option for patrol drive (#314)
• Remove support for the patrol.toml config file (#313)

• Don't require host and port to be defined in patrol.toml or passed in as command-line arguments (#301)
• Print cleaner, more readable logs when native action fails (#295)

• Restart flutter drive on connection failure (#280)
• Rename --devices to --device to be more consistent (#280)
• Populate homepage field in pubspec.yaml (#254)

• Fix handling native permissions on older Android API levels (#260)

• Fix URL of artifact storage (#259)

• Rename to patrol_cli (#258)

• Add new --wait argument which accepts the number of seconds to wait after the test finishes (#251)
• Make maestro drive run all tests (#253)

• Migrate iOS AutomatorServer to a more stable HTTP server, which doesn't crash randomly (#220)
• Add new packageName and bundleId fields to maestro.toml
• Add new arguments to the tool: --package-name and --bundle-id

• Add support for handling native permission requests on Android (#232)
• Fix Android AutomatorServer suppressing all accessibility services (#235)

• Now maestro_cli will clean up after itself, either when it exits normally or is stopped by the user (#209):
  • port forwarding is automatically stopped
  • artifacts are automatically uninstalled
• pod install is automatically run when iOS artifacts are downloaded (macOS only) (#206)

• Fix not working on Windows because of flutter command not being found

• Fix problem with project not building because of a breaking change in package:mason_logger dependency

• Fix issue with CI

• Add support for physical iOS devices

• Fix bug with APKs failing to force install when certificates don't match, this time once and for all

• Fix bug with APKs failing to force install when certificates don't match

• Rename MAESTRO_ARTIFACT_PATH environment variable to MAESTRO_CACHE
• Add maestro devices command
• Some work made under the hood to enable support for iOS

• Support maestro_test 0.4.0

• Fix dependency resolution problem

• Improve output of maestro drive

• Fix a crash which occured when ADB daemon was not initialized

• Fix a crash which occured when ADB daemon was not initialized
• Make it possible to add --dart-defines in maestro.toml
• Fix templates generated by maestro bootstrap

• Automatically inform about new version when it is available
• Add maestro update command to easily update the package

• Add support for new features in maestro_test 0.3.0

• Add support for new features in maestro_test 0.2.0

• Allow for running on many devices simultaneously
• A usual portion of smaller improvements and bug fixes

• Be more noisy when an error occurs
• Change waiting timeout for native widgets from 10s to 2s

• Fix a bug which made flavor option required
• Add --debug flag to maestro drive, which allows to use default, non-versioned artifacts from $MAESTRO_ARTIFACT_PATH

• Fix typo in generated integration_test/app_test.dart
• Depend on package:adb

• Set minimum Dart version to 2.16.
• Fix links to package:leancode_lint in README

• Add --template option for maestro bootstrap
• Add --flavor options for maestro drive
• Rename maestro config to maestro doctor

• Add --device option for maestro drive, which allows you to specify the device to use. Devices can be obtained using adb devices

• Fix maestro drive on Windows crashing with ProcessException

• Fix a few bugs

• Fix maestro bootstrap on Windows crashing with ProcessException

• Make versions match AutomatorServer

• Nothing

• Add support for maestro.toml config file

• Split maestro and maestro_cli into separate packages
• Add basic, working command line interface with

• Initial version