8

Phantom.js was abandoned, maintainer recommended to switch to headless Chrome. Headless Chrome does not use CPU resources to repaint the screen, so try how many separate browser sessions you can run on same machine - you might not see the difference between just one headed and headless Chrome, it might be just few percent of the load.


5

I think Peter is right, it does not need the OS to draw the rendered page, might be some what faster. Something you will probably only notice if you run a lot in parallel. But the main point is you can run it on a virtual machine without an Desktop Operating System, saving you lots of memory and thus costs as those VMs are much cheaper per hour. Also if ...


4

One of the disadvantages of using SaaS for regression testing is that you need to allow outside organization access to your pre-production test environment. In most organizations, it has significant part of real production information, which can be security risk. Even if you de-identify user data (scramble addresses, phones, names etc) in pre-production ...


3

You just ask karma to run Chrome headless. It's no longer necessary to create it out of ChromeOptions Here are the first few lines from my karma.conf.js module.exports = function (config) { config.set({ browsers: ['ChromeHeadless'], // Chrome ChromeHeadless .... You get this with the karma-chrome-launcher, which it sounds like you ...


3

Angular has some great tooling for running tests, namely Karma and Protractor. By default (at least when using Angular CLI) they run using Chrome. So when you execute the tests from command-line, it will pop open a browser window where the tests execute. This works well enough, but sometimes you either don’t want to see that browser window pop open or you ...


2

PhantomJS was abandoned, author recommends to switch to headless Chrome. Parallelization proposed by dzieciou might help, but you will be spending time to improve wrong tool.


2

There are multiple solutions: Use faster locators like id and name. See What makes a good selenium locator? Run your tests in parallel Change part of your tests to REST API tests, component and unit tests If you're using your tests as gateway control, e.g., to decide whether to deploy a build to next environment or production, separate your tests. Use short ...


1

When writing a framework in c# are there any recommended tools for this that I can look into? Its totally depends on you aim and requirement as per current trend Selenium is most popular now days. You can refer the official site. You can configure the test to be execute in headless mode (even in chrome and Firefox) easily. I'm not actually concerned with ...


1

After looking through https://docs.oracle.com/javase/tutorial/2d/images/saveimage.html https://stackoverflow.com/questions/19871955/java-io-filenotfoundexception-the-system-cannot-find-the-file-specified https://stackoverflow.com/questions/47600505/chrome-headless-doesnt-work https://stackoverflow.com/questions/16239130/java-user-dir-property-what-exactly-...


1

To debug, first try to take a screenshot in headless mode when you arrive at the button. Then take another screenshot before the test fails or after you click the button. It really looks like you pressed the button but the next screen wasn't triggered. Try to add a timeout before you press the submit button. Maybe 30 seconds, you can reduce this later, ...


1

This did it for me wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add - sudo sh -c 'echo "deb http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list' sudo apt-get update


1

HtmlUnit does not have screenshot function, as the page is not rendered. Here is the feedback from the developers on a similar question: HtmlUnit is a headless browser, and makes no attempt to render content. This is the reason that the HtmlUnitDriver does not support the TakesScreenshot interface. If you need to take screenshots, then I'd ...


1

Based on what you have described, a feasible (it may not be the best) approach can be: Discuss with the project owner(s) regarding which images of which sections have the highest business value, e.g. worth of testing effort. For each element that is to be tested, produce a object model for it, e.g. what element it is? where it is physically on a page? other ...


Only top voted, non community-wiki answers of a minimum length are eligible