feat: @wdio/xvfb#14663
Conversation
create-wdio
eslint-plugin-wdio
@wdio/allure-reporter
@wdio/appium-service
@wdio/browser-runner
@wdio/browserstack-service
@wdio/cli
@wdio/concise-reporter
@wdio/config
@wdio/cucumber-framework
@wdio/dot-reporter
@wdio/firefox-profile-service
@wdio/globals
@wdio/jasmine-framework
@wdio/json-reporter
@wdio/junit-reporter
@wdio/lighthouse-service
@wdio/local-runner
@wdio/logger
@wdio/mocha-framework
@wdio/protocols
@wdio/repl
@wdio/reporter
@wdio/runner
@wdio/sauce-service
@wdio/shared-store-service
@wdio/smoke-test-cjs-service
@wdio/smoke-test-reporter
@wdio/smoke-test-service
@wdio/spec-reporter
@wdio/static-server-service
@wdio/sumologic-reporter
@wdio/testingbot-service
@wdio/types
@wdio/utils
@wdio/webdriver-mock-service
@wdio/xvfb
webdriver
webdriverio
commit: |
5a220c0 to
9c9383f
Compare
1e3fa75 to
f03f695
Compare
|
Marked as ready for review for some early feedback. Still need to consider the following, I think we need manual tests at a minimum:
Specifically need to verify that (1) xvfb is being run on a system where it is available, and (2) xvfb is installed and run on a system where it is not available. These should be verified on different Linux distros. |
christian-bromann
left a comment
There was a problem hiding this comment.
Some initial feedback.
Co-authored-by: Christian Bromann <git@bromann.dev>
|
Conceptually I am wondering if these E2Es are more like smoke tests, will see if they fit better there. Also need to add tests for the other distros, and fix the perm errors. UPDATE: changed my mind, these don't fit well with the existing smokes. |
|
Still need to go over the docs but I think it's getting there. So far the only documentation I added is the Also, do we want this integrated anywhere else or is it just applicable to the local-runner? I will update the electron service to use it directly in the script / non-testrunner-based case - see webdriverio-community/wdio-electron-service#1132. |
|
Note to self: verify that the case where xvfb fails to start is handled gracefully. I think some configurable number of retries would make sense, as I have been experiencing occasional failing jobs on Linux CI in this regard (using xvfb-maybe). UPDATE: prototyping this approach in webdriverio-community/wdio-electron-service#1133... Seems to work: https://github.com/webdriverio-community/wdio-electron-service/actions/runs/16756083118/job/47439022995?pr=1133 |
|
Hey goosewobbler 👋 Thank you for your contribution to WebdriverIO! Your pull request has been marked as an "Expensable" contribution. We've sent you an email with further instructions on how to claim your expenses from our development fund. We are looking forward to more contributions from you in the future 🙌 Have a nice day, |
Proposed changes
Creating a new package
@wdio/xvfbfor running XVFB on linux systems where appropriate to avoid confusing Chromium errors. See #14501Types of changes
Checklist
Backport Request
//: # (The current
mainbranch is the development branch for WebdriverIO v9. If your change should be released to the current major version of WebdriverIO (v8), please raise another PR with the same changes against thev8branch.)v9and doesn't need to be back-ported#XXXXXFurther comments
Reviewers: @webdriverio/project-committers