search

nightwatchjs / nightwatch

Integrated end-to-end testing framework written in Node.js and using W3C Webdriver API. Developed at @browserstack
https://nightwatchjs.org
MIT License
11.79k stars 1.31k forks source link

Issue with Internet explorer - Time out waiting for element body... #650

Closed Jezternz closed 8 years ago

Jezternz commented 9 years ago

I seem to be getting an issue while trying to run Nightwatchjs with IE. I am running the basic test found on the nightwatch frontpage (The google one).

The console only gives me the standard:

Starting selenium server... started - PID:  3664

[Test1] Test Suite
==================

Running:  Demo test Google
 ? Timed out while waiting for element <body> to be present for 10000 millisecon
ds.  - expected "visible" but got: not found
    at Object.module.exports.Demo test Google (C:\Users\Josh\Desktop\WebUnitTest
sIETest\tests\test1.js:5:8)
    at Module.call (C:\Users\Josh\Desktop\WebUnitTestsIETest\node_modules\nightw
atch\lib\runner\module.js:60:34)
    at C:\Users\Josh\Desktop\WebUnitTestsIETest\node_modules\nightwatch\lib\runn
er\testcase.js:96:29
    at _fulfilled (C:\Users\Josh\Desktop\WebUnitTestsIETest\node_modules\nightwa
tch\node_modules\q\q.js:834:54)
    at self.promiseDispatch.done (C:\Users\Josh\Desktop\WebUnitTestsIETest\node_
modules\nightwatch\node_modules\q\q.js:863:30)
    at Promise.promise.promiseDispatch (C:\Users\Josh\Desktop\WebUnitTestsIETest
\node_modules\nightwatch\node_modules\q\q.js:796:13)
    at C:\Users\Josh\Desktop\WebUnitTestsIETest\node_modules\nightwatch\node_mod
ules\q\q.js:556:49
    at runSingle (C:\Users\Josh\Desktop\WebUnitTestsIETest\node_modules\nightwat
ch\node_modules\q\q.js:137:13)
    at flush (C:\Users\Josh\Desktop\WebUnitTestsIETest\node_modules\nightwatch\n
ode_modules\q\q.js:125:13)
    at process._tickCallback (node.js:355:11)

FAILED:  1 assertions failed (15.278s)

----------------------------------------------------
TEST FAILURE: 1 assertions failed, 0 passed (15.356s)
 ? test1
   - Demo test Google
     Timed out while waiting for element <body> to be present for 10000 millisec
onds. - Expected "visible" but got: "not found"

Everything is up to date, I am running: Nightwatch - 0.8.3 Selenium - 2.47.1 Internet Explorer Selenium driver - 2.47.0 Java - 1.8.0_60 Node - 4.1.0 Internet Explorer - 11.0.18 Windows 7 x64 Pro

I have played around with it a fair amount with different versions of the driver, selenium and nightwatch but seem to have different problems with the different versions.

I have also configured IE as described here: https://code.google.com/p/selenium/wiki/InternetExplorerDriver#Required_Configuration

I am pretty much out of ideas, so am hoping this will be recognizable.

The full debug log I am seeing is here: https://gist.github.com/Jezternz/ad73736ddc27943907b7

beatfactor commented 9 years ago

Maybe you can run it with --verbose and post the output?

On Tue, Sep 22, 2015 at 5:45 AM, Joshua McLauchlan <notifications@github.com

wrote:

I seem to be getting an issue while trying to run Nightwatchjs with IE. I am running the basic test found on the nightwatch frontpage (The google one).

The console only gives me the standard:

Starting selenium server... started - PID: 3664

[Test1] Test Suite

Running: Demo test Google ? Timed out while waiting for element to be present for 10000 millisecon ds. - expected "visible" but got: not found at Object.module.exports.Demo test Google (C:\Users\Josh\Desktop\WebUnitTest sIETest\tests\test1.js:5:8) at Module.call (C:\Users\Josh\Desktop\WebUnitTestsIETest\node_modules\nightw atch\lib\runner\module.js:60:34) at C:\Users\Josh\Desktop\WebUnitTestsIETest\node_modules\nightwatch\lib\runn er\testcase.js:96:29 at _fulfilled (C:\Users\Josh\Desktop\WebUnitTestsIETest\node_modules\nightwa tch\nodemodules\q\q.js:834:54) at self.promiseDispatch.done (C:\Users\Josh\Desktop\WebUnitTestsIETest\node modules\nightwatch\node_modules\q\q.js:863:30) at Promise.promise.promiseDispatch (C:\Users\Josh\Desktop\WebUnitTestsIETest \node_modules\nightwatch\node_modules\q\q.js:796:13) at C:\Users\Josh\Desktop\WebUnitTestsIETest\node_modules\nightwatch\node_mod ules\q\q.js:556:49 at runSingle (C:\Users\Josh\Desktop\WebUnitTestsIETest\node_modules\nightwat ch\node_modules\q\q.js:137:13) at flush (C:\Users\Josh\Desktop\WebUnitTestsIETest\node_modules\nightwatch\n ode_modules\q\q.js:125:13) at process._tickCallback (node.js:355:11)

FAILED: 1 assertions failed (15.278s)

TEST FAILURE: 1 assertions failed, 0 passed (15.356s) ? test1

  • Demo test Google Timed out while waiting for element to be present for 10000 millisec onds. - Expected "visible" but got: "not found"

Everything is up to date, I am running: Nightwatch - 0.8.3 Selenium - 2.47.1 Internet Explorer Selenium driver - 2.47.0 Java - 1.8.0_60 Node - 4.1.0 Internet Explorer - 11.0.18 Windows 7 x64 Pro

I have played around with it a fair amount with different versions of the driver, selenium and nightwatch but seem to have different problems with the different versions.

I have also configured IE as described here: https://code.google.com/p/selenium/wiki/InternetExplorerDriver#Required_Configuration

I am pretty much out of ideas, so am hoping this will be recognizable.

The full debug log I am seeing is here: https://gist.github.com/Jezternz/ad73736ddc27943907b7

— Reply to this email directly or view it on GitHub https://github.com/nightwatchjs/nightwatch/issues/650.

Jezternz commented 9 years ago

Thanks so much for digging into this beat,

Selenium debug looks pretty similar: https://gist.github.com/Jezternz/71853c5c21458130a390 Verbose console log has a lot more: https://gist.github.com/Jezternz/c5667f11d8dbece67c7f

Looking at the logs it appears as though the "wait for body to be ready" appears to be failing, which is confusing as running this does actually open an IE window and browse to google. Which makes me think this is probably a connection issue between selenium and IE?

beatfactor commented 9 years ago

Can you disable the log colors and update the gist? Set disable_colors to true: http://nightwatchjs.org/guide#basic-settings

Jezternz commented 9 years ago

Updated, cheers.

sknopf commented 8 years ago

Check out this stackoverflow post: http://stackoverflow.com/questions/24746777/selenium-nosuchwindowexception-in-ie-11

Looks like you may need an additional setting for IE11

beatfactor commented 8 years ago

Is this still actual?

Jezternz commented 8 years ago

I started from scratch and seem to have resolved the issue, the console is no longer printing out the error, however nightwatchjs seems to get stuck on the "There is a problem with this website’s security certificate.". I will continue digging into this.

I have set acceptSslCerts:true Nightwatchjs: 0.8.18 IEDriver: IEDriverServer_Win32_2.53.0

Jezternz commented 8 years ago

Closing this, as https://github.com/nightwatchjs/nightwatch/issues/794, is a better description now.