1

I keep getting this error randomly while running the protractor tests (1 out of 6 or 1 out of 3 for other people in my team) "Element is not clickable at point".

This is how my specs look like

 describe('My suite that breaks', function(){
        it('sp start page', function() {
            //some other stuff
        });
        it('select something from dropdown', function(){
            waitForElement(by.css('button[data-organization="none"]')).click();
            waitForElement(by.css('a[data-organization="somevalue"]')).click();
            //some other stuff
        });

Some utilitary function defined some other place

waitForElement(locator, timeout = config.timeouts.wait){
    var elem = element(locator);
    var isClickable = protractor.ExpectedConditions.elementToBeClickable(elem);
    browser.wait(isClickable, timeout, 'Waiting for element  \'' + locator + '\' timed out');
    return elem;
}

My HTML

<div class="btn-group">
<button type="button" class="btn-dropdown inner-shadow" data-organization="none">
  Some butt text<span class="caret"></span>
</button>
<ul class="dropdown-menu" role="menu">
<li><a href="#" class="no-selection" data-organization="none">None</a></li>
<li><a href="#" data-organization="something">Something</a></li>
</ul>
</div>

This happens randomly. It is not an xvfb issue since I have full Ubuntu desktop. The item is viewable, no overlay, no refresh.

$cat /etc/issue
Ubuntu 14.04.5
$node --version
v6.8.0
$npm list -g|grep protractor
└─┬ protractor@4.0.9
$webdriver-manager status
[13:49:58] I/status - selenium standalone version available: 2.53.1 [default]
[13:49:58] I/status - chromedriver version available: 2.22 [default]
[13:49:58] I/status - android-sdk is not present
[13:49:58] I/status - appium is not present
$/opt/google/chrome/chrome --version
Google Chrome 54.0.2840.59 unknown

How to debug this? What to do?

Community
  • 1
  • 1
ddreian
  • 1,766
  • 5
  • 21
  • 29
  • 1
    Take a screenshot when the exception occurs to understand why it's not clickable. It could be due to a fixed bar, a screen too small, an animation, a popup on top... – Florent B. Oct 14 '16 at 14:57
  • Possible duplicate of [Debugging "Element is not clickable at point" error](http://stackoverflow.com/questions/11908249/debugging-element-is-not-clickable-at-point-error) – MikeJRamsey56 Oct 14 '16 at 16:54

0 Answers0