Add tests for driver and app

[ShootingKing-AM]

Add some testing for driver and app

• Research for CI Based vr testing solutions

• OpenVR E2E Test possiblity - Yes Possible

• Future TODO: Unit Testing

• Object: Need to Test ALVR (atleast mobile end) on ci before pushing changes

  • Auto Sync in Alvr-phonevr repo
  • and Dependabot will pickup changes - which will CI in PhoneVr Repo

[ShootingKing-AM]

• Compile Test with gradle github-actions in CI CI: Build Driver and Server #119
• Local AVD based testing
  • PhoneVR Legacy server is already AVD compatible
  • Make ALVR Server AVD compatible for automation testing
  • Local AVD SS Test tests: Implemented basic SS instrumentation tests for critical app paths #121
• App installation (Instrumentation testing) on max and min version with screenshot for atleast startup (can borrow what has been implemented for aw-android)
• Run AVD Test - SS Test at Start Screen max and min versions in CI
  • Upload(comment ss) to PR - Keep Updating/editing comment with run
    • could not run ALVRActivityTest on CI ALVRActivity MacOS AVD Host Crash #127
    • Rest implemented in ci: Implement basic instrumentation tests #126
• Basic e2e with ALVR Server, SteamVR Home, Send acelometer cmds via adb shell (?) using Docker
  • Local
  • In CI
    • Issue is windows Github runners dont have VM enabled (needs citation) - Hard to setup Android Testing E2E and SteamVR dosent support other OSes except windows
      • There is an option on ghactions.job.service / .container to run a docker container - can dockerize SteamVR and run it as a service
        • Limitations: must use a Linux Runner; Linux dosent have KVM enabled for now atleast
          • reactivecircus/android emulator - asks not to use linux Why running the action on Linux VMs is slow ReactiveCircus/android-emulator-runner#46 - even after testing, linux - AVD dosent boot up in default time - timesout
      • Windows github runners some times have HyperV-T and emulator --accel-check sometimes gives success message accel: 0 Please disable Hyper-V before using the Android Emulator. Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot.WHPX (10.0.20348) is installed and usable. accel saying WHPX(or similar hypervisor) is installed - and sometimes it just exists with code 4 saying VT-X is not supported accel: 4 Android Emulator requires an Intel processor with VT-x and NX support. (VT-x is not supported) - weird inconsistency
        • Like Linux, Testing with bare metal avdmanager installation / emulator commands makes the task timeout (adb does not detect emulator has started up even after 30mins)
      • Another option is to test CirrusCI (https://dev.to/ychescale9/exploring-cirrus-ci-for-android-434) - which has default KVM enabled on its linux/macos runners
        • Need to check if it has ghactions-like job.service /.container ?
        • Does it consistently give emulator --accel-check 0 ? unlike github actions - then can dockerize SteamVR and run it on windows it self
    • Have to test manually, locally - may introduce unknowns as compared to Fresh Docker Image like Github-actions runners
      • Make Dockerimage distribute to test

[ShootingKing-AM]

• E2E for PhoneVR Legacy server