1 - remove the work/ from the URL. Unlike urlblast.ini, it is not needed, just the base URL for the server.
2 - For the user data dir and extension parts of the command line, leave the %WPTDIR% and %PROFILE% strings from the original, they will be expanded automatically
3 - You shouldn’t need the cache= line (as long as you use %PROFILE% for the user_data_dir).
I’m assuming the path to the chrome exe is correct (I expect #1 was the main problem)
sorry, one more change - in wptdriver.ini it should be “Key=”, not “Location Key=”. Sorry for changing the names from urlblast.ini but we were taking the opportunity to try to make things a little cleaner on the new platform.
Now, it works ok with Chrome, and shows the results right. But when I click “Create video” button, it cannot create video, just staying the “Video will be create shortly” screen. (When I change to use IE for Test Agent, creating video is ok).
Do we need any plugin for creating video when using Chrome for Test Agent?
Are the IE and Chrome agents connecting to the same server (you can run both wptdriver and urlblast at the same time, they will make sure only one is running a test at a time)?
Only urlblast knows how to render videos right now so you need at least one instance of it running, even if it isn’t connected to a location. The videos can be rendered by any location it doesn’t need to be the same one that ran the test.