Dusk with Selenium not working with Laradock

Question

I'm running Dusk to test my Laravel application. I've recently switched to Laradock which took some time to set it all up as I have little experience with Docker, but it all seems to be working now. Except that Selenium doesn't seem to be working as it should.

I start and open my workspace like this:

sudo docker-compose up -d nginx postgres beanstalkd selenium
sudo docker-compose exec --user=laradock workspace bash

and then

php artisan dusk

1) Tests\Browser\SuccessLoginTest::test_user_can_login
Facebook\WebDriver\Exception\NoSuchElementException: no such element: Unable to locate element: {"method":"css selector","selector":"body textarea[name='email']"}
  (Session info: headless chrome=75.0.3770.90)
For documentation on this error, please visit: https://www.seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: 'f8c1169cd1a3', ip: '172.18.0.3', os.name: 'Linux', os.arch: 'amd64', os.version: '5.4.7-100.fc30.x86_64', java.version: '1.8.0_212'
Driver info: driver.version: unknown

I get a screenshot of the failing test showing the websiteand on it the and element it can't seem to find. Before I switched to Laradock everything was working properly, so the problems seems to be with Selenium. My setup looks like this and I use Laravel 5.7.28

protected function driver()
{
    $options = new ChromeOptions();

    $options->addArguments([
        '--headless',
        '--no-sandbox',
        '--disable-gpu',
        '--window-size=1920,1080',
        '--ignore-certificate-errors'
    ]);

    $capabilities = DesiredCapabilities::chrome();
    $capabilities->setCapability(ChromeOptions::CAPABILITY, $options);

    if (env('USE_SELENIUM', 'false') == 'true') {
        return RemoteWebDriver::create(
            'http://selenium:4444/wd/hub', $capabilities
        );
    } else {
        return RemoteWebDriver::create(
            'http://localhost:9515', $capabilities
        );
    }

score 1 · Answer 1 · answered Jan 12 '20 at 12:39

This error message...

Facebook\WebDriver\Exception\NoSuchElementException: no such element: Unable to locate element: {"method":"css selector","selector":"body textarea[name='email']"}
  (Session info: headless chrome=75.0.3770.90)
For documentation on this error, please visit: https://www.seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: 'f8c1169cd1a3', ip: '172.18.0.3', os.name: 'Linux', os.arch: 'amd64', os.version: '5.4.7-100.fc30.x86_64', java.version: '1.8.0_212'
Driver info: driver.version: unknown

...implies that the NoSuchElementException was raised during your program execution.

A bit of details about your Test Configuration interms of chromedriver version would have helped us to debug your issue in a better way. However you need to take care of a couple of things:

The purpose of the argument --disable-gpu was to enable google-chrome-headless on windows platform. It was needed as SwiftShader fails an assert on Windows in headless mode earlier. This issue was resolved through Headless: make --disable-gpu flag unnecessary. As you are on laravel / laravel-dusk / laradock on linux, you need to remove the line of code:
```
'--disable-gpu' // applicable to windows os only
```
As per your question as you are using chrome=75.0. you need to ensure:
- ChromeDriver is updated to ChromeDriver v75.0 as per the Release Notes of chromedriver=75.0
Having said that, ideally you need to ensure that:
- JDK is upgraded to current levels JDK 8u222.
- Selenium is upgraded to current levels Version 3.141.59.
- ChromeDriver is updated to current ChromeDriver v79.0.3945.36 level.
- Chrome is updated to current Chrome Version 79.0 level. (as per ChromeDriver v79.0 release notes)
- Clean your Project Workspace through your IDE and Rebuild your project with required dependencies only.
- (WindowsOS only) Use CCleaner tool to wipe off all the OS chores before and after the execution of your Test Suite.
- (LinuxOS only) Free Up and Release the Unused/Cached Memory in Ubuntu/Linux Mint before and after the execution of your Test Suite.
- If your base Web Client version is too old, then uninstall it through Revo Uninstaller and install a recent GA and released version of Web Client.
- Take a System Reboot.
- Execute your @Test as non-root user.
- Always invoke driver.quit() within tearDown(){} method to close & destroy the WebDriver and Web Client instances gracefully.

Reference

You can find a relevant detailed discussion in:

Hats off to your time and effort.Most people likely avoid such longer question and It seems you have all the time and answer whenever there is any problem related to selenium.Such a dedicated contributor +1 — KunduK, Jan 12 '20 at 13:06
Thanks indeed for the help so far. I'm not sure if I understand your remark 'A bit of details about your Test Configuration in terms of chromedriver version '. Isn't the error showing it is using 75.0.3770.90 ? As you state that there is a newer version I'm now trying to use v79. At the moment I did a pull on Laradock and are rebuilding. I will see if that is going to solve any issues. I understand about the NoSuchElement error, but the problem is that the element is there. Somehow it is not found. — Matthieu, Jan 12 '20 at 13:19
@Matthieu `headless chrome=75.0.3770.90` implies **chrome** _Browser_ version. Whereas `Driver info: driver.version: unknown` at some point **chromedriver** version was not detected. — undetected Selenium, Jan 12 '20 at 13:24
Could that be a clue that it is unknown there? The Selenium Webdriver hub says it using chromedriverVersion": "75.0.3770.90. Seem to be stuck though on updatin to v79. — Matthieu, Jan 12 '20 at 15:34
No, **75.0.3770.90** is the `chrome=75.0.3770.90` version and can't be the **chromedriver** version. — undetected Selenium, Jan 12 '20 at 15:51

Dusk with Selenium not working with Laradock

1 Answers1

Reference