Protractor + chrome driver: Element is not clickab

问题:

Hi I am having some trouble getting a basic protractor test to work.

My setup:

• I use requirejs so I init angular using angular.bootstrap(), not the ng-app attr. According to protractor docs this is not supported out of the box, but seems to work fine for tests that don' involve clicking.

• Protractor conf.json:

  "use strict";
  exports.config = {
      specs: '../E2ETests/**/*.js',
      chromeOnly: true,
      getPageTimeout: 30000,
      allScriptsTimeout: 30000
  }
  

• I use some third party jquery plugs which I wrap in directives, I suspect these might be part of the issue.

The test:

"use strict";
describe('When clicking should add stuff', function () {
    var ptor;
    beforeEach(function () {
        browser.get('https://localhost/myApp');
        ptor = protractor.getInstance();
    });
    it('add stuff', function () {
        // If I comment this, the test pass. 
        element(by.id('add-stuff-button')).click();
        // This does not matter fails on the line above..
        expect(browser.getTitle()).toBeDefined();
    });
});

The error:

UnknownError: unknown error: Element is not clickable at point (720, 881). Other element would         receive the click: <div class="col-md-5 col-md-offset-5">...</div>
(Session info: chrome=37.0.2062.124)
(Driver info: chromedriver=2.10.267521,platform=Windows NT 6.1 SP1 x86_64)

Thoughts

The chromedriver do find the button, because if I change the id it complains that no element is found. So I think the problem is that the button moves from its initial position. As the element(***) function should wait for angular to be done, I suspect that its the third party plugins that might interfere as they might not use angular api's fetching data etc. So angular think its done but then the third party plug populates and moves stuff around.

Any ideas what to do? If the third party plugs is the problem, can I somehow tell angular that third party stuff is going on and then later tell it when its done?

Thx Br Twd

回答1:

You should set window size in your config file

onPrepare: function() {
  browser.manage().window().setSize(1600, 1000);
}

回答2:

Following worked fine for me:

browser.actions().mouseMove(element).click();

Edit: If above does not work try chaining perform() method too(I got this as an edit suggestion, I have not tested it but somebody could verify it and comment)

browser.actions().mouseMove(element).click().perform();

回答3:

This happens if the chrome window is too small, try to add inside the beforeEach

browser.driver.manage().window().setSize(1280, 1024);

回答4:

Or simply use the Actions class:

browser.actions().mouseMove(elem).click().perform();

回答5:

Maybe It is not applicable in your case, but I've encountered the same problem and based on Milena's answer I've been looking for another element obscuring my button (in my case, a dropdown menu in the top right of my screen).

It appears to be the Connected to Browser Sync notification message sent by browsersync, launched by Gulp. The message vanished after a short time, but after my onClick() call.

To remove the notification, in my gulpfile, I've added the notify: false param when initializing browsersync:

browserSync.init(files, {
    server: {
        baseDir: "dist",
        index: "index.html"
    },
    notify: false
});

回答6:

I fix this problem by using browser time sleep.

browser.driver.sleep(3000)

before giving click button

回答7:

Had the same issue but was not related to the window size but had to wait for ngAnimation to end.

So I had to wait until the element was clickable with.

    const msg = 'Waiting for animation timeout after 1s';
    const EC  = new protractor.ProtractorExpectedConditions();
    await browser.wait(EC.elementToBeClickable(model.elements.button.checkCompliance), 1000, `${msg} panel`);
    await model.elements.button.checkCompliance.click();

@note - I am using async/await node 8 feature, you could just as well convert this to regular Promises. Also using ProtractorExpectedConditions instead of ExpectedConditions see documentation

回答8:

I had the same error and purely adjusting the screen size did not fix it for me.

Upon further inspection it looked as though another element was obscuring the button, hence the Selenium test failed because the button was not (and could not be) clicked. Perhaps that's why adjusting the screen size fixes it for some?

What fixed mine was removing the other element (and later adjusting the positioning of it).

回答9:

Other way, you can try this:

this.setScrollPage = function (element) {

    function execScroll() {
        return browser.executeScript('arguments[0].scrollIntoView()',
            element.getWebElement())
    }

    browser.wait(execScroll, 5000);
    element.click();
};

回答10:

This works better than specifying the window size, in case you test need to run on multiple displays.

browser.manage().window().maximize();

回答11:

You could also try turning off any debug tools you might be using. I was using Laravel and debugbar and had to set APP_DEBUG to false.

回答12:

From Gal Malgarit's answer,

You should set window size in your config file

onPrepare: function() {
  browser.manage().window().setSize(1600, 800);
}

If it still doesn't work you should scroll to the element's location

browser.executeScript('window.scrollTo(720, 881);');
element(by.id('add-stuff-button')).click();

回答13:

Note that this was sometime caused by a top navigation bar or bottom navigation bar / cookie warning bar covering the element. With angular 2, when clicking it scrolls until the element is only just on page. That means that when scrolling down to click something, if there is a bottom navigation, then this will obstruct the click. Similarly, when scrolling up it can be covered by the top navigation.

For now, to get around the scrolling up, I am using the following:

browser.refresh();
browser.driver.sleep(3000);

I made sure that I removed the bottom bar by clicking to close it before the test started.

回答14:

You can define the desired screen resolution through your protractor configuration file (e.g. protractor.conf.js or config.js) for consistent test behavior.

For example with Chrome browser:

exports.config = {
  specs: [
    // ...
  ],
  capabilities: {
    browserName: 'chrome',
    chromeOptions: {
      args: [
        '--window-size=1600,900',
        '--headless'
      ]
    }
  }
  // ...
}

Explanations

• window-size argument will launch Chrome with a 1600 by 900 window.
• headless will launch headless Chrome, allowing you to have your tests run with the specified window size (1600 by 900) even if your screen resolution is lower than that.

You may want to have two configurations, one for developers (without headless mode) who always have a high resolution screen and one for build servers (headless mode) where screen resolution is sometimes a mystery and could be lower than what your application / test is designed for. Protractor configuration file are javascript and can be extended to avoid code duplication.