Visor Testing & Feedback - An Expedited Journey

[VestigeJ]

Pre-amble - the current QA information collected isn’t likely to change a lot when FE ships, we know it’s likely we will want to script up a bunch of functions and templates to export data quickly. Other than getting information from Visor itself (ADB dump?) we can work the other end of this with focus on the existing desktop server side.

Good scripts will likely incorporate information from many places on the systems:

• Hardware characteristics (processors involved, system memory, system load, etc).
• Charging behavior can surface weird issue’s depending on the power input cleanliness (if not using default in the box).
• Low power settings if there are any to conserve battery life at play on either device.
• OS Versions
• Application Versions
• Network topology for wifi direct testing (question for the team here actually is how peer to peer is handled after on the same wifi.
• common language and terms can help immensely for QA feedback.
• community support matrix for bespoke hardware deployments? (Jetson Nano's/RPi's et al).

I'd propose we setup multiple directories for the major OS platforms that mirror the Agent Installs

• Linux
  • scripts
    • check configuration for known bad configs
    • export useful QA information in a pre-defined template
    • anonymize sensitive user data on behalf of script runner
    • save information to local file to attach to email in case offline
• MacOS
  • scripts
    • check configuration for known bad configs
    • export useful QA information in a pre-defined template
    • anonymize sensitive user data on behalf of script runner
    • save information to local file to attach to email in case offline
• Windows
  • powershell
    • check configuration for known bad configs
    • export useful QA information in a pre-defined template
    • anonymize sensitive user data on behalf of script runner
    • save information to local file to attach to email in case offline

These are higher level goals it would be good to see if the Immersed Team already has their own debug information templates/scripts 👀 https://immersed.helpscoutdocs.com/article/23-connection-troubleshooting-linux