AutoDriver - Our E2E testing is no longer working
We were using AutoDriver, found here: https://developer.oculus.com/documentation/unity/ts-autodriver/ This no longer seems to work. The command that causes issues is: "adb shell debug.oculus.autoDriverApp". This will always return: "/system/bin/sh: debug.oculus.autoDriverApp: inaccessible or not found". This has seriously affected our testing, as we used this system for our E2E testing. If anyone has information on this issue, good or bad, please reach out. My team is small and heavily relied on this system.2.3KViews1like3Comments
Can't find *.autodriver file when running RecordAutoDriverInputs.bat
I ran RecordAutoDriverInputs.bat and recorded some activity in our app. The batch file outputted confirmation that the *.autodriver file had been created, but I couldn't find it in either the folder where the folder where the batch file was run from, nor anywhere on our Quest 2 headset. The *.logcat.txt file was generated successfully. Any ideas of how I can get it to generate the *.autodriver file?1KViews3likes1Comment
Autodriver introduces offset during playback
Hello there fellas. We have a problem. We use autodriver for E2E testing. In our old codebase everything worked fine (Unity 2018.3.4 + VRTK) in our new we see an offset between recording and playing back .autodriver files which renders autodriver useless. This is w Unity: 2020.3.21 XR Core Utilities 2.0.0 XR Interaction Toolkit 1.0.0-pre.8 XR Legacy Input helpers 2.1.8 XR Plugin Management 4.0.7 Does anyone have any ideas?1.2KViews0likes1Comment