Upgrading from 0.9.x to 1.0.8 throws an error on waitForElementVisible #1864
Comments
gregoryduckworth
changed the title
|
Your config and platform details? |
|
Platform is: Config is: |
|
And have you tried using chromedriver directly, without selenium? It's also strange that you have to set |
|
Updated my config to (below) and still have the same issues
|
|
Getting the same error through BrowserStack only. Here's my config for Browserstack: const selenium = {
host: process.env.SELENIUM_HOST,
port: process.env.SELENIUM_PORT
}
const nightwatchConfig = {
src_folders: ['./test/e2e/tests'],
output_folder: ['./test/e2e/reports'],
selenium: {
start_process: false,
host: selenium.host,
port: selenium.port
},
test_settings: {
default: {
desiredCapabilities: {
'browserstack.user': process.env.BROWSERSTACK_USERNAME,
'browserstack.key': process.env.BROWSERSTACK_ACCESS_KEY,
'browserstack.local': true,
'resolution': '1440x900',
'os': 'Windows',
'os_version': '10',
'browserName': 'Chrome',
'browser_version': '62.0',
'browserstack.selenium_version': '3.11.0',
'build': `${process.env.BROWSERSTACK_BUILD_NAME}`
},
skip_testcases_on_fail: false,
screenshots: {
enabled: true,
path: './test/e2e/screenshots'
}
}
}
}
// Code to copy seleniumhost/port into test settings
for (var i in nightwatchConfig.test_settings) {
var config = nightwatchConfig.test_settings[i]
config.webdriver = {
webdriver_host: selenium.host,
webdriver_port: selenium.port
}
}
module.exports = nightwatchConfigBrowserstack settings: And this is my local config that I use before pushing. And in my local config, it works as expected. nightwatch_config = {
src_folders : ['./test/e2e/tests'],
output_folder : ['./test/e2e/reports'],
custom_commands_path : '',
custom_assertions_path : '',
page_objects_path : '',
globals_path : '',
selenium: {
start_process : true,
server_path : './test/e2e/bin/selenium-server-standalone-3.12.0.jar',
log_path : '',
port : 4444,
cli_args : {
'webdriver.chrome.driver': './test/e2e/bin/chromedriver',
'webdriver.gecko.driver': './test/e2e/bin/geckodriver'
}
},
test_settings : {
default : {
launch_url : 'http://.../offers',
webdriver: {
webdriver_host: 'localhost',
webdriver_port: 4444
},
silent: true,
screenshots : {
enabled : true,
path : './test/e2e/screenshots'
},
globals: {
devServerURL: 'http://.../offers'
},
desiredCapabilities: {
browserName: 'chrome',
javascriptEnabled: true,
acceptSslCerts: true,
elementScrollBehavior: 1
}
},
chrome : {
desiredCapabilities: {
browserName: 'chrome',
javascriptEnabled: true,
acceptSslCerts: true,
elementScrollBehavior: 1
}
},
firefox: {
desiredCapabilities: {
browserName: 'firefox',
javascriptEnabled: true,
acceptSslCerts: true,
marionnette: true,
elementScrollBehavior: 1
}
}
}
};
module.exports = nightwatch_config |
|
@WilliamDASILVA do you have a verbose log output as well? |
|
I do but it does not provide extra informations about the issue. |
|
We are coming across similar problems with We have scaled back to the sample Browserstack test, here: https://www.browserstack.com/automate/nightwatch#sample-test Same problem in Chrome v60-69 (letting Browserstack pick Chromedriver). Works fine in Firefox on Browserstack. Works intermittently when running Selenium/Chromedriver/Chrome.app installed locally on OSX. And the result: I'm not convinced this is a Nightwatch issue, so apologies for posting here, if it's not. We'll keep digging tomorrow. |
|
@gmcdev which nightwatch version are you using? |
|
@beatfactor, We were on |
|
We're also running into this on Saucelabs. Chrome is fine while firefox, ie, and safari all fail with this error.
|
|
@Everlag Ok, could you also post a verbose log output with a failed test? Thanks. |
|
Please try with v1.0.11. |
|
Tried with Chrome tests still works fine. Relevant snippet from code Verbose(some redacted with ...; nothing that should impact the correctness) |
|
NW 1.0.11, Chrome on BrowserStack, running the sample BrowserStack test: Result: In Firefox 61, the |
|
@gmcdev what is your browserstack config? |
|
Upgraded to 1.0.11 and get the same error as @gmcdev
|
|
@beatfactor same config as my previous post -- thanks for looking into it! |
|
@gmcdev the issue is that you're setting |
|
@beatfactor - ouch, that is embarrassing, thanks for the catch. Changing it to It appears BrowserStack needs to update their docs: https://www.browserstack.com/automate/nightwatch We will follow-up there. Thanks again~ |
|
@gmcdev no problem. I should add |
|
I'm closing this, if anyone still experiences this issue, please re-open. |
|
Thanks @beatfactor, I had to move |
|
@beatfactor The problem still exists on The probem seems to be on the URL, see the
|
|
Still running into this issue, I've had |
|
@irobayna thanks, I'll look into it. |
|
Switched from saucelabs to browserstack for unrelated reasons, continuing to experience this issue. However, we're now seeing firefox successfully complete and edge fail; firefox, previously, did not work with saucelabs. The URL problem is the same as @irobayna. |
|
For the record, my specific issue was resolved in the |
|
Any update on this? We're blocked on bringing our integration tests to CI. |
|
@Everlag There will be a fix for edge posted this week. |
|
Similar problem in v1.0.11 when testing on a mobile device on BrowserStack: |
|
@beatfactor What's the status on that fix and is it expected to potentially address other issues? |
beatfactor
added a commit
that referenced
this issue
Oct 8, 2018
|
All our tests in browserstack that dosn't use chrome or firefox as the browser now fails in the same way as described above. ETA on the fix you are working on would be greatly appreciated @beatfactor 😄 |
|
@beatfactor I'm experiencing this same issue. Using BrowserStack, tests work fine in Firefox and (sometimes) Chrome, but IE, Edge, Safari and mobile testing break when trying to perform any selection. This is the error messages I get: I changed Let me know if there's any other information I can provide you. Cheers! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My current scenario is that I am in the process of upgrading our test repository from 0.9 -> 1.0 however after following the wiki and getting the tests to start, some basic actions are performed correctly, such as navigating to the right page and providing feedback on that. However when the tests hit a
waitForElementVisiblethe console reports the errorError while running .isElementDisplayed() protocol action: undefined.The test steps are as follows:
Running the command with
--verbosereports:The text was updated successfully, but these errors were encountered: