I successfully installed wpt-www server and wpt-agent on the same 64 bit machine.
I am able to see my agent instances [ local --> Chrome ; local --> firefox , local--> IE] .
Set UP :
Agent and Server on the same 64 bit windows machine.
I have my agent sitting in C: /wpt-agent
My server folder wpt-www is inside the /xammp/htdocs.
I have configured port 81 , and hence using http://localhost:81 inside the wptdriver and urlBlast settings.
My /install check looks good :
Local : Local
Local-URLBlast : Test Location - IE 8 - 2 agents connected
Local-WPTDriver : Local - 1 agents connected
1.1. Can I have the server and the agent install on the same machine given that it is a 64 bit windows machine
2.When I start the test, it just shows waiting in front of queue.
3. The agent window show DNS cache flush =1
4. Then Chrome and Firefox both close
Can someone please tell me what is going on ? I love this tool but the documentation only brought me this far. I hope to get some hand-holding from this point on from this forum*
Here is an update : I changed a few things for the test to start working:
Changed “localhost” with IP address “127.0.0.1”, kept the port same at 81, seemed to work.
Kick started the wptdriver .
I still have 3 issues /question. 2 of which I am attaching the screenshots
I am getting a slice of the wpt home page in my film strip long with the site under test. ( attached :filmstrip-view.jpg) . Is there some things I need to take care so that purely my site under test is captured.
I got a video error . Attaching video-error.jpg for more info . I got this only once when I running the test via chrome and simulating a chrome agent.
I see the test waits for 240 secs before spitting any results out. Is there a way to change that to a lesser time ?
I am now on my way to see if I can script these to batch up multiple tests.
1 - Make sure you’re using a 32-bit version of Chrome (and Firefox). WPT injects binary code into the browser process and it only supports 32-bit right now.
2 - Submitting tests on the same machine where the tests run (particularly using the same browser) is probably going to cause all sorts of strange behavior like you are seeing. You can run the server and test agents on the same machine but it pretty much expects to have the machine to itself. If you do want to do testing locally, use a different browser than the one running the tests and minimize it right after you submit until the test is finished.