[FEATURE] Does maestro-runner have any plans to support HarmonyOS (it use hdc is similar to android's adb)

[tsdking]

Problem Statement

Harmonyos mobile phones already have a large number of users. If maestro-runner can support it, it will be able to fully cover the mobile operating system, which is an advantage.

Proposed Solution

Suggestion 0 (Recommendation): Maestro-runner officially supports harmony, which involves App Lifecycle Commands such as launchApp. There may be a certain adaptation cost, but official support should be the most reliable solution

Other plans (minimum official changes)

Suggestion 1: maestro-runner supports executing javascript such as runscript. This is a great feature. Then if runscript supports executing shell commands, it can call any cli tool, such as harmony's hdc

Suggestion 2: Do not make any changes to the runscript. You only need the platform parameter of maestro-runner to support harmony (currently reporting an error directly), and then when writing yaml, forward the hdc command through the js script of runscript for local execution. This is achievable.

Use Case

Explain how you would use this feature.

Example

maestro-runner --platform harmony test test-harmony.yaml 

  maestro-runner 1.1.1 - by DeviceLab.dev
  Fast, lightweight Maestro test runner
  Star us on GitHub

Setup
────────────────────────────────────────
  ✓ Found 1 test flow(s)
Execution
────────────────────────────────────────
Error: failed to create driver: unsupported platform: harmony

Alternatives Considered

Describe any alternative solutions or workarounds you've considered.

Additional Context

Add any other context, screenshots, or references here.

[omnarayan]

Hi @tsdking — thanks for the thoughtful write-up! HarmonyOS support is definitely on my radar, and you've done a great job breaking down the options.

Quick bit of honesty on my end: getting a HarmonyOS device in India is genuinely tough. Huawei pulled out of the Indian consumer market a while back, so the only way to get one is through grey-market imports at a pretty steep premium. I'm hesitant to ship a driver and claim HarmonyOS support when I don't have a device on my desk to actually validate against — that feels like it'd do more harm than good in the long run.

That said, I really don't want to just leave this as a "no," so here are two paths I'd bae happy to pursue:

Short term — I can take a look at your Suggestion 1 (exposing shell/exec capability through runScript). That gives you a clean way to call out to hdc directly from your flows, without us needing to maintain any Harmony-specific code. It's a small, contained change and should unblock your use case pretty quickly.

Longer term — if you'd be open to contributing a HarmonyOS driver yourself, I'd be genuinely excited to review and merge it. You clearly know hdc well, and the driver interface in maestro-runner is already nicely abstracted (have a look at pkg/core/driver.go — Android, iOS, and web each implement it independently). Adding a Harmony implementation would be a well-scoped piece of work, and I'm happy to point you at the relevant files, answer questions as you go, and give early feedback on the design.

Either route works for me — let me know which direction feels right on your end!