kotlin-graphics / openvr

OpenVR SDK
http://steamvr.com
BSD 3-Clause "New" or "Revised" License
37 stars 0 forks source link

Failing tests - Unable to read VR Path Registry from ~/.config/openvr/openvrpaths.vrpath #1

Open stephenohair opened 6 years ago

stephenohair commented 6 years ago

Hi Giuseppe,

I'm having an issue building your code on Ubuntu using gradle. Both unit tests are failing when trying to initialise the vr api. Please note I don't have steam or any openvr api runtime currently installed on my system.

Based on TesteEventLogger output it seems that a pre-requisite to executing the tests on this project is to install openvr api runtime. Would it be better if the tests were configured to use either a generic or platform-specific openvrpaths.vrpath file?

[ERROR] [system.err] Unable to read VR Path Registry from /home/steve/.config/openvr/openvrpaths.vrpath 11:30:16.284

[ERROR] [system.err] Unable to read VR Path Registry from /home/steve/.config/openvr/openvrpaths.vrpath

How did you get around this issue in your Travis build? I checked your travis build and can't see any line suggesting a step requiring openvr be installed prior to running the build.

Cheers,

Steve

elect86 commented 6 years ago

Hi Steve,

I didn't test the lib anymore on Ubuntu since more than a year now..

Would it be better if the tests were configured to use either a generic or platform-specific openvrpaths.vrpath file?

Sure, what do you have in mind exactly?

How did you get around this issue in your Travis build? I checked your travis build and can't see any line suggesting a step requiring openvr be installed prior to running the build.

I simply skip any test if I detect I'm running on Travis, it's crap, but I didn't find any better alternative so far

Ps: maybe this issue could be interesting?

If you want we can work together to improve this aspect, I'll send you an invitation

stephenohair commented 6 years ago

This might be useful or at least start some ideas how a test harness in Travis might be set up for Linux: https://github.com/rust-openvr/openvr-testing-driver https://github.com/ValveSoftware/steam-runtime https://github.com/ValveSoftware/SteamVR-for-Linux

Alternatively a separate mock interface might be an idea that's called explicitly by integration tests only. I'm sure there's a lot more to consider here though so I'll think some more on it.

elect86 commented 6 years ago

Interesting resources.. I have very limited time at the moment, so I'm forced to postpone a deep analysis to the matter

However, if you want to experiment, you are very welcome :)