test: Test runner for native tests

[marcelklehr]

No description provided.

[marcelklehr]

@copilot Fix the android-appium workflow in this PR

[Copilot]

@copilot Fix the android-appium workflow in this PR

Addressed in db3d8d2 by enabling KVM access before starting the Android emulator in the workflow, which should prevent the boot timeout seen in CI.

[marcelklehr]

@copilot Fix the android appium test flow created in this PR

[Copilot]

@copilot Fix the android appium test flow created in this PR

Fixed in 2b3c42f by starting Appium with --allow-insecure chromedriver_autodownload, so the Android WEBVIEW context can fetch a matching Chromedriver in CI instead of failing during context switch.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• appium.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[marcelklehr]

@copilot Now appium doesn't start, can you fix it?

[Copilot]

@copilot Now appium doesn't start, can you fix it?

Fixed in 1383524. Appium 3 requires insecure features to be scoped as <driver>:<feature>, so I changed the workflow to use uiautomator2:chromedriver_autodownload instead of the unscoped flag that was causing Appium to exit on startup.