I am currently having an issue with OpenTap loading the Python virtual environment correctly during sessions, but skipping over the virtual environment during global initialization. Any tap CLI command, as well as the Runner startup process before a session is created, appears to bypass the configured virtual environment. I believe this is causing a “Caught exception loading: No module named name”. It only loads the provided python DLL path. I can see the path skipping the virtual environment under PythonEngine.PythonPath in the Runner logs. Once a session is created the logs show the path to the virtual environment followed by the path to the DLL. My plugins load correctly and the test plans are executed successfully during sessions. Could it be skipping the virtual environment path during global initialization and therefore the cause for the module not found exception?
This causes runner based subject like “Set/Get ComponentsSettings” to fail because it does not load the virtual environment when it is loading the Python plugins. Is this is a known issue? OpenTap not adding the virtual environment’s at Runner startup?