-
Notifications
You must be signed in to change notification settings - Fork 31
Description
Hi David,
I'm trying to replay scripts such that I can document how its done for the New Relic Synthetics crowd. I have a test script from sauce labs that I've used many times with se-builder v2 (Attached: full_example.json.txt). It loads into v3.1.2 just fine, but when I try to replay the script, there are certain steps at which it throws an error like TypeError: r.currentStep is undefined. I can delete that step but it happens for a few others.
Here are the commands in that script for which it's failing. I don't know if there's anything special about these commands or that its a command-specific issue, but it fails on these steps consistently.
{
"type": "verifyCurrentUrl",
"negated": true,
"url": "http://google.com"
}
{
"type": "assertPageSource",
"source": "${page_source}"
},
{
"type": "verifyCookiePresent",
"name": "test_cookie"
},
{
"type": "verifyCookiePresent",
"negated": true,
"name": "test_cookie"
},
Also, I tried running this with Selenium Server Standalone v2.5 and v3.0beta, and with both the ChromeDriver and GeckoDriver, all to the same result. Interestingly, when using the GeckoDriver I get a little bit more info out of the stdout, not sure if it's relevant though:
[Child 8069] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2046
[Child 8069] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2046
Environment details:
- Mac OS X 10.11.6
- Firefox 48
- Java(TM) SE Runtime Environment (build 1.8.0_74-b02) (HotSpot, 64-bit)
- Selenium Builder 3.1.2
- Tried with both selenium-server-standalone-2.53.1.jar & selenium-server-standalone-3.0.0-beta3.jar
- Tried with both GeckoDriver 0.10.0 and ChromeDriver 2.24 (switched by passing "chrome" as the browser string in the "Run on Selenium Server" dialog
Let me know if you need any further details to recreate the issue or dig into it.
Thanks,
Seth
