Codeception undefined index: ELEMENT error

Question

i am using Codeception for acceptance testing. On my local pc i have no problems to run the tests with selenium and chromedriver. Until 1 week, it works also fine at my git, but now, there comes this error.

"[PHPUnit\Framework\Exception] Undefined index: ELEMENT"

local it is working fine without errors.

I already searched this error and found an tip, that i have to start selenium with "-enablepassthrough false". But this does not really works.

Before 1 week with all the same setup, it works fine.

this is my acceptance.suite.yml:

actor: AcceptanceTester
modules:
    enabled:
        - WebDriver:
            url: 'https://website.com' 
            host: 'selenium__standalone-chrome'
            port: 4444
            browser: chrome 
            window_size: 1920x1080

Possible duplicate of [error "\[PHPUnit\Framework\Exception\] Undefined index: ELEMENT" when running codeception with WebDriver](https://stackoverflow.com/questions/56491910/error-phpunit-framework-exception-undefined-index-element-when-running-code) — Naktibalda, Jun 12 '19 at 07:30

score 3 · Answer 1 · answered Jan 23 '20 at 09:53

3

For Chrome/ChromeDriver v79 setting w3c to false in acceptance.suite.yml helped:

modules:
  enabled:
    - WebDriver:
        capabilities:
          chromeOptions:
            w3c: false

answered Jan 23 '20 at 09:53

Pavel Alazankin

1,325
1
12
22

That's the only option working for me on Mac with chrome. – Ibrahim.H Jan 13 '21 at 20:01
anyone know how to declare this for FF? – Robert Sinclair Dec 01 '21 at 21:16

score 2 · Accepted Answer · answered Jun 12 '19 at 07:32

This error message...

[PHPUnit\Framework\Exception] Undefined index: ELEMENT

...implies that the ChromeDriver's click() through Codeception is having an issue.

As per @reinholdfuereder's comment within the discussion facebook/php-webdriver - W3C WebDriver protocol support:

When using default W3C protocol, then the Codeception (v2.5.6) test fails with Undefined index: ELEMENT in waitForElement() operation.
When using legacy protocol, then the test succeeds for waitForElement() operation, which is followed by a seemingly also successful click() operation, but fails in the waitForElementNotVisible() operation.
Codeception's click() operation is translated into clickElement WebDriver command that is seemingly no more supported by ChromeDriver v75.

Solution

If you are using ChromeDriver v75.x and Chromium v75.x and you are seeing this error, you need to pass an additional chromeOptions w3c set to true.

Outro

You can find a couple of detailed discussion in:

score 0 · Answer 3 · answered Jun 18 '19 at 06:09

As @DebanjanB explained, setting the said option is a solution and this is what you get by updating facebook/php-webdriver to version >= 1.7.0

I think an even more solid solution (or habit) for your application is to use a specific docker image.

Your yaml makes me guess that you're using the selenium/standalone-chrome docker image. With their latest release (3.141.59-palladium) they updated the included Chrome version from 74 to 75 (see: https://github.com/SeleniumHQ/docker-selenium/releases).

Your local machine probably still runs an older version with Chrome 74 so no problems there. But whenever you rebuild the docker machine (e.g. when using some CI environment) you get the latest version. In this case a new Chrome version. Which "forces" you to also upgrade your php machine with a new facebook/php-webdriver.

I'd suggest to specify a version of the image to prevent these unwanted side effects, like

image: selenium/standalone-chrome:3.141.59-oxygen

or, if you've already made it run with Chrome 75, 3.141.59-palladium.

Codeception undefined index: ELEMENT error

3 Answers3

Solution

Outro