Skip to content

Provide a strategy to prevent problems with test running on Linux without graphics subsystem #4461

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
miherlosev opened this issue Nov 8, 2019 · 2 comments · Fixed by #5340
Labels
TYPE: enhancement The accepted proposal for future implementation.
Milestone

Comments

@miherlosev
Copy link
Collaborator

Then somebody runs the tests on Linux without any graphic subsystem (CI machines, docker, etc.), it gets an unclear message about browser disconnection.

The cause of the problem - it's impossible to run the browser in non-headless mode on Linux with a graphics subsystem.

We can fix it using many ways:

  • inform a customer about its situation
  • automatically start xvfb if it's necessary
  • switch to headless mode
  • etc.

We need to discuss it and choose the best approach.

@miherlosev miherlosev added the TYPE: enhancement The accepted proposal for future implementation. label Nov 8, 2019
@miherlosev miherlosev changed the title Provide a strategy to prevent problems with Xvfb buffer Provide a strategy to prevent problems with test running on Linux without graphics subsystem Nov 8, 2019
@miherlosev
Copy link
Collaborator Author

#4138

@miherlosev
Copy link
Collaborator Author

After discussion with team, we decided to extend 'Cannot establish connection..' message with the phrase You run <browser_name> browser with graphic interface in Linux without graphic subsystem. Try to run <browser_name> in headless mode. For more information see https://devexpress.github.io/testcafe/documentation/guides/concepts/browsers.html#test-in-headless-mode.

@miherlosev miherlosev added this to the Sprint #58 milestone Jun 22, 2020
@AndreyBelym AndreyBelym modified the milestones: Sprint #58, Sprint #59 Jun 23, 2020
@AndreyBelym AndreyBelym modified the milestones: Sprint #59, Sprint #60 Jul 8, 2020
@AndreyBelym AndreyBelym modified the milestones: Sprint #60, Sprint #61 Jul 23, 2020
@AndreyBelym AndreyBelym linked a pull request Jul 23, 2020 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TYPE: enhancement The accepted proposal for future implementation.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants