Problem on Windows

[kaystrobach]

Hello,

i started to create tests in Dalek on OSX, and then we tried to test them on Windows as well.

What happens:

• Chrome opens
• Form fields are filled

[2556:6332:0519/155517:ERROR:ipc_channel_win.cc(405)] pipe error: 232
[2556:6332:0519/155517:ERROR:ipc_channel_win.cc(405)] pipe error: 232
[2556:6332:0519/155517:ERROR:ipc_channel_win.cc(405)] pipe error: 232

• intended click is never sent to chrome.

Same happens for IE, Firefox and PhantomJS

I would appriciate any hint how to get it working on windows :smile:

[asciidisco]

Hey, the error reports you see are "normal", they come form the chromedriver.exe, and for some reason you can't disable/silence the output as you can do with the chromedriver binary for *nix systems.

But that doesn't take care of your problem, if I git this right, your test runs fine on OSX in at least PhantomJS/Chrome; but when you run the exactly same test on Windows the click action is never executed, not in Chrome & not in Phantom (reducing to 2 browsers here, should be enough to track down the issue & makes it easier)?!

I do need some more information:

• Windows version
• Chrome version
• Windows arch (32 or 64 bit)
• the contents of your test (best would be a stripped down version, which runs against a public page)
• Node.js version (from both systems)

Hope we can track the issue down.

[kaystrobach]

    Windows version
        Windows: Windows 7 Ultimate (Service Pack 1)
        OSX: latest: 10.9.3
    Chrome version
        Windows:35.0.1916.114 m
        OSX: 35.0.1916.114
    Windows arch (32 or 64 bit)
        Windows:64 bit
        OSX: 64bit
    the contents of your test (best would be a stripped down version, which runs against a public page)
        schick ich mit
    Node.js version (from both systems)
        Windows:0.10.28
        OSX: v0.10.28

I would like to send you the tests as private mail only :smile:

[asciidisco]

It seems to be an issue caused by the system architecture (and therefor downloading the correct driver files on windows); I also would suggest not sending me your testfiles (not even in private), but better a stripped down version that reproduces the failure, that will shorten the time I need to reproduce the issue.

Thanks in advance.

Btw.: You can still send me the reduced testcases via mail then (dalekjs@asciidisco.com) it is

[kaystrobach]

For some reason it seems to work now - so i would be fine - if you close the issue. In the meantime we switched to SSL, as stated in the mail.

[asciidisco]

I was about to dig deeper into the files you send me via mail tomorrow. But great that it works now :+1:

If you have any other questions, I will try my best to answer them in time.

[kaystrobach]

thank you for your great work - if the error occurs again i would reopen this issue if you are fine with that ;)

Btw. do the tests follow the intention how you would have made them, if not i appreciate a comment on them ;)

[asciidisco]

Will do & report ;)