Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

Chromedriver support in Qt 5.12?



  • I am attempting to build chromedriver for the QtWebEngine as part of Qt5.12, which is based on Chromium 69.0.3497.128. QtWebEngine is successfully cross-compiled for 32bit embedded Linux target. No chromedriver is built as part of this build however. I cannot find any details on how to enable it or if it is supported in Qt5.12, or if it plans to be supported in the future.

    Looking at the source, I can see chromedriver in the QtWebEngine source (qtwebengine/src/3rdparty/chromium/chrome/test/chromedriver), however it is just a mostly empty directory with a BUILD.gn file. Looking at the Chromium project at 69.0.3497.128 there is a full source for chromedriver (https://github.com/chromium/chromium/tree/69.0.3497.128/chrome/test/chromedriver).

    Attempts at dropping this source into the QtWebEngine tree do not yield it being automatically picked up to be built. Attempting to use the QtWebEngine gn/ninja tools to build the Chromium chromedriver source does not seem to be directly supported either.

    Is there a Qt supported approach to including chromedriver (or any webdriver implementation) in the QtWebEngine build?



  • No the code is stripped out of our build. That is why the dir is mostly empty (we need to leave the BUILD.gn file in there, because GN is a terrible build system which deals poorly unused code pointing at nonexisting parts)



  • No the code is stripped out of our build. That is why the dir is mostly empty (we need to leave the BUILD.gn file in there, because GN is a terrible build system which deals poorly unused code pointing at nonexisting parts)



  • @Allan-Jensen thanks for the clarification (completely agree about gn). Is there a recommended approach for supporting a webdriver implementation for QtWebEngine?

    Edit to rephrase so it doesn't seem like I am just re-asking the same question again :
    Was chromedriver removed for a specific reason? I.e. if I tried to add it back in would I expect to run into the problems that led to it being removed in the first place? Is it expected that a chromedriver built from upstream Chromium project be compatible with the Qt fork for QtWebEngine? Does Qt have a different test interface that would replace the need for a webdriver implementation?

    Feature request tracked here:
    https://bugreports.qt.io/browse/QTBUG-82046


Log in to reply