Skip to content
This repository has been archived by the owner on Jan 18, 2022. It is now read-only.

Choose emulator/device to launch android app on + refactor mobile launcher #1194

Merged
merged 9 commits into from
Oct 18, 2019

Conversation

paulbalaji
Copy link
Contributor

@paulbalaji paulbalaji commented Oct 15, 2019

Description

  • added ability to choose which emulator/device to launch apk on
  • heavily refactored MobileLauncherWindow to minimise duplicated code
  • added some comments here and there

image
image

Tests

I've tested all possible emulator/device, local/cloud and android/ios combinations possible on both windows and mac (enumerated below).

Will re-validate this at the end

  • Android
    • Windows
      • emulator local
      • emulator cloud
      • device local
      • device cloud
    • MacOS
      • emulator local
      • emulator cloud
      • device local
      • device cloud
  • iOS
    • Simulator local
    • Simulator cloud
    • device local
    • device cloud

Documentation

How is this documented (for example: release note, upgrade guide, feature page, in-code documentation)?

  • update docs on how to launch mobile clients
  • changelog

Primary reviewers

If your change will take a long time to review, you can name at most two primary reviewers who are ultimately responsible for reviewing this request. @ mention them.

@improbable-prow-robot improbable-prow-robot added jira/no-ticket Indicates a PR has no corresponding JIRA ticket A: mobile Area: Mobile integration size/XL Denotes a PR that changes 300-599 lines, ignoring generated files. labels Oct 15, 2019
@zeroZshadow
Copy link
Contributor

LGTM, can you add a screenshot of the current look in the description?

@paulbalaji paulbalaji merged commit df927f6 into develop Oct 18, 2019
@paulbalaji paulbalaji deleted the feature/android-workflow-parity branch October 18, 2019 12:58
jessicafalk pushed a commit that referenced this pull request Nov 15, 2019
* When launching worker, create logs directory to prevent the native server launch script failing
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A: mobile Area: Mobile integration jira/no-ticket Indicates a PR has no corresponding JIRA ticket size/XL Denotes a PR that changes 300-599 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants