selenium.click([xpath to object])
Selenium click method seems to be screwed up for me. It recognises the button I want to click and thinks it clicks it. But nothing happens on the screen. The next line involves clicking another button on the next screen. It fails because it cant locate the button because the first click hasn't actually happened.
[EDIT]
It looks like It just fails to click after the screen changes. It will click the log in button fine, and load the new screen. The next click fails, but if i give it a gentle push(IE click the button for it) all the followin clicks in the script run fine. So it seems to be a problem with a click after a screen change?
I had a similar problem and this code worked for me:
mouseOver(locator);
mouseDownAt(locator, "10,10");
mouseUpAt(locator, "10,10");
I wrapped it up in a clickButton() method and use it instead of click()
you can try this:
WebElement element = driver.findElement(By.id("button"));
JavascriptExecutor executor = (JavascriptExecutor)driver;
executor.executeScript("arguments[0].click();", element);
If you're doing it on Internet Explorer, there is a known bug that its window must be foremost. Some people get past this with doing another event which makes the window get focus like clicking twice or maximising, etc. etc.
Related
Hello Fellow Stack Overflow members and coders,
I am trying to make an automation script using Selenium WebDriver on Instagram where I want to follow every member a particular account is following.
I am stuck at a point where after navigating to user's profile (who's follower I want to follow) when I click on "following" link a new window opens and it contains all the members this user follows (as shown in following screenshot):
Window opened after clicking "following" link
Now as you can see in above window only first few followers are initially loaded and then as you keep on scrolling down the users keeps on getting loaded.
I am completely lost here on how can I move the focus to this new jquery kind of window and keep on scrolling down until the full list is loaded and then find once full list is loaded, click on follow button for each user.
Your help would be really appreciated in this regard.
I have tried various options like moving the mouse over to the window and clicking at blank location and then using Keys.Arrow_Down multiple times, finding first Follow button and then keep on pressing down button etc but it doesn't seem to be right approach and it doesn't work. Kindly help me solve this issue.
what if you...
Using a while, get all the visible elements in a list, move using JavascriptExecutor to the last of the element in the list, and keep getting the elements(doing the same, moving to the last pos in the list) until you reach the number(this is the while condition) of following(or following-1 if he/she follows you)
(JavascriptExecutor)driver).executeScript("arguments[0].scrollIntoView();", webElementInList);
There's a menu item that I want to click.
However just before this click, in my test flow I have a modal open, which prevents clicking on the menu item. Also, when closed, the modal will fade instead of disappearing instantly.
What I do is close the menu item and then place a wait for the menu item to be clickable, before performing the click:
WebDriverWait wait = new WebDriverWait(getDriver(), time);
wait.withMessage(message);
try {
wait.until(ExpectedConditions.elementToBeClickable(locator));
} catch (Exception e) {
Logging.logException(e);
}
clickOn(locator);
However this does not work, as I'm running each time into the following exception:
org.openqa.selenium.WebDriverException: unknown error: Element is not clickable at point (158, 565). Other element would receive the click: <div class="globalpopup with-data slideout">...</div>
I also have Selenium set-up to take a screenshot each time an exception occurs and in the screenshot I can clearly see that the modal is in the process of fading out.
So the close button for it has been clicked, but at this point I'm thinking the wait should come into effect and pause execution until the modal fully disappears and the menu item can be clicked. Which does not happen.
Now I usually fix this by adding a bit of sleep time, as it's quite predictable how long it takes the modal to fade out. However I'd really like to figure out a more elegant solution, which can apply in all situations.
My understanding is that elementToBeClickable does not account for when the element is covered by another element, which I find quite silly. Is there a way to simulate such a wait (notCoveredByOtherElement), as it's exactly what I'd need?
P.S. I'm using Selenium 2.53. Have not tried v3 yet, although I'd happily make the effort to start switching to it if someone can confirm that this case is handled properly in this new version.
I also faced this issue number of time and tried some solution which always worked for me.
1-Updated chrome driver to latest one 2.23
2-Get the coordinate then click on the link or button
3-Try to click using Y coordinates
// Find an element
WebElement elementToClick = driver.findElement(By.xpath("Your xpath"));
// Scroll the browser to the element's Y position
((JavascriptExecutor)driver).executeScript("window.scrollTo(0,"+elementToClick.getLocation().y+")");
// Click the element
elementToClick.click();
// Find an element
WebElement elementToClick = driver.findElement(By.xpath("Your xpath"));
// Scroll the browser to the element's Y position
((JavascriptExecutor)driver).executeScript("window.scrollTo(0,"+elementToClick.getLocation().y+")");
// Click the element
elementToClick.click();
I have documented all in below link kindly check
Solutions for Element is not clickable in Selenium
Is there a difference between testing perspective and not usability, on clicking elements with selenium like this:driver.findElement(By.id("foobar")).click();
instead of using coordinates and the robot class.
Example: If an element is not clickable because of a bug, robot will not be able to click it. Will selenium be able to click it ?
Selenium tries as much as possible to emulate what a regular user can and cannot do. When you use findElement(...).click() Selenium will raise an exception if operation cannot be performed. For instance, if an element exists in the DOM but is not displayed, an exception will be raised. And note that Selenium's .click() will try to scroll elements. If you ask it to click an element that is not visible but could be visible by scroll it, Selenium will scroll to bring it into view.
Also note that Selenium will usually take the element's coordinates and perform a click at those coordinates. So the idea that a moving element will always be hit by findElement(...).click() (expressed in this answer) is incorrect. Using findElement minimizes the window between which the coordinates are acquired and the click event is sent, but it does not completely eliminate it. The reason that Selenium works with coordinates is, again, to reproduce what a user would do. The user would see the element, move the mouse to the coordinates of the element, and click on it. If the element has an transparent overlay over it, then the overlay will get the click, rather than the element. This works because Selenium clicks at the coordinates rather than send a click directly to the element that you selected with findElement.
If you are using Robot to perform the click, the stakes are roughly the same as above, with a few caveats:
Trying to click moving elements is more of an issue because the window of time between acquiring the coordinates and performing the click is greater.
Robot does not know how the DOM is structured so won't scroll elements for you.
Rogério Peixoto pointed out that you can use JavaScript to perform the click. This will cause the event handler for click to be called for the element, irrespective of whether a user would be in fact able to access the element. This can allow clicking on elements that are not otherwise clickable but I would not do this unless there are overriding reasons to do so. I've gone over the difference between Selenium's click and the JavaScript click in this answer.
If an element is not clickable because of a bug, robot will not be able to click it. Will selenium be able to click it?
It depends on what the bug is that is preventing the click. I would suggest that you use element.click() in almost all cases because it's more maintainable. For coordinate clicks, what if the element moves? Then you have to update your script with the new position where element.click() will just work. Another issue with coordinate clicking, what if your element moves and another one is in its place? That will likely cause your script to fail but will be very hard to track down. An example might be an unexpected popup that covers the element to be clicked. Now your coordinate click will hit the popup and eventually cause an error/failure. If you do element.click() you will at least get an error that another element would receive the click. You can then track down what is getting in the way from debugging.
Selenium clicks in my experience click an element within a browser window, where as Robot click seem to click whatever is on the desktop at the time. Personally I would recommend you try to use Selenium clicks where possible as you can specify the window in which you are clicking.
Using this:
driver.findElement(By.id("foobar")).click();
Means that you will click the element with the foobar id regardless where it is.
If you use coordinates, you won't be able to click the element if they change their position.
Updating answer due to your updated question:
I'm not quite sure where you're trying to get with this.
In Selenium, if the element is visible it will receive the click event, if not you'll have an exception.
You could force click it with javascript:
WebElement element = driver.findElement(By.id("foobar"));
((JavascriptExecutor)driver).executeScript("arguments[0].click();", element);
But it won't trigger the an eventual javascript event registered to that button, you would have to fire it manually.
I am automating a web application using selenium webdriver and java. It has few mouse over elements which I am not able to automate. Mouse over works well and newly visible elements locate properly when I record and play in Selenium IDE but same is not working when I run in eclipse. I have automated similar mouse over elements earlier but facing difficulty in automating this. I have attached screenshot of a web application and the code for mouse over elements and here I am not able to mouse over on "Configuration" menu and select "Configure Hierarchy Metadata". It would be really great if anybody could help me out in this!! Let me know if any more details needed.
Thanks in advance.
This is a very common issue. You need to make sure you are interacting with the element that has the hover listener..
In this case, it looks like it is the <a> that is receiving the hover. Try moving to element (hovering over):
By.cssSelector("ul.topmenu li:nth-child(2) > a[title='Configurations']");
In order to achieve this, you will first have to hover on element(say - element1) which makes element to be clicked(say - element2) on visible and then click on the option from list -
Actions actions = new Actions(driver);
actions.moveToElement(element1).moveToElement(element2).click(element2).build().perform();
Specs:
Windows 7;
selenium 2.39.0;
Java - Eclipse
I'm currently using Selenium to test a webApp through three different browsers (Chrome, IE9 and Firefox).
The webApp has a menu bar, and there are located dropdown menus (classic).
I need to set the mouse over one item of that menu bar and wait for a dropdown menu to appear, then I need to click in one of the dropdown menu items.
My code:
WebElement div_menu = driver.findElement(By.xpath("//div[text() = 'Trigger of the dropdown menu']"));
WebDriverWait wait = new WebDriverWait(driver, 300);
Actions builder = new Actions(driver);
builder.moveToElement(div_menu).build().perform();
WebElement item_to_click = wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("Link_inside_the_dropdown_menu")));
item_to_click.click();
The funny stuff occurs when I start the test. (FYI Browsers come up one by one, that is to say, all tests are performed for one browser before going on with other one, not threaded.)
If the mouse pointer is over the browser (because they are started not full maximized) at the time the tests are performed, then here are the results:
Chrome: div_menu seems to get the mouseover (because of a css style change), but for too short, so that dropdown menu never appears
IE9: throws this exception: org.openqa.selenium.ElementNotVisibleException: Cannot click on element, but mainly, div_menu gets the mouseover, so dropdown menu is displayed. In spite of this, item_to_click it's not clicked at all (btw, I don't think the exception is the issue cause). And besides, it's like an invisible mouse keep laying over the div_menu, because when I move the real mouse, dropdown menu blinks as if div_menu lose the hover and get it back every time I stop moving the real mouse.
Firefox: Works as it's supposed to.
Now, let's see what happens when I left the mouse outside the browser window.
Chrome: works
IE9: works
Firefox: div_menu seems to get the mouseover (because of a css style change), but for too short, so that dropdown menu never appears
As you can see, the code is the same for the three of the browsers. The funny variable here is the mouse_in_browser and mouse_out_browser.
I can't imagine what the problem could be.
If you need any extra info, please don't hesitate.
Thank you very much in advance!
I managed to get Firefox to work no matters where the physical mouse is.
I initialized it this way:
//Firefox initialization
FirefoxProfile profile = new FirefoxProfile();
//explicitly enable native events(this is mandatory on Linux system, since they
//are not enabled by default
profile.setEnableNativeEvents(true);
WebDriver driver = new FirefoxDriver(profile);
This did the trick for me regarding Firefox. Not yet the others two.
Source: Selenium WebDriver mouse actions moveToElement doesn't raise mouseout event on Firefox Linux