You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We consume playwright as a library for multiple automation projects. Many end-users have multiple automation projects installed on their desktop. It would be nice to have an optional parameter that allows us to point to a central location for the .playwright folder so that we don't need to have this 70mb folder installed under each project folder.
Currently this folder has to be in a specific location otherwise an unhandled exception is thrown. -
(Driver not found: C:\Users\clmeye\source\repos\MsPlaywrightTestHarness.playwright\node\win32_x64\playwright.cmd)
We initially found a way around this by updating the playwright code our self, but this is very time consuming to do so for every playwright update. An option to point to an alternate path for the .playwright folder would be a welcomed update.
The text was updated successfully, but these errors were encountered:
We consume playwright as a library for multiple automation projects. Many end-users have multiple automation projects installed on their desktop. It would be nice to have an optional parameter that allows us to point to a central location for the .playwright folder so that we don't need to have this 70mb folder installed under each project folder.
Currently this folder has to be in a specific location otherwise an unhandled exception is thrown. -
(Driver not found: C:\Users\clmeye\source\repos\MsPlaywrightTestHarness.playwright\node\win32_x64\playwright.cmd)
We initially found a way around this by updating the playwright code our self, but this is very time consuming to do so for every playwright update. An option to point to an alternate path for the .playwright folder would be a welcomed update.
The text was updated successfully, but these errors were encountered: