Support a special run-type of HEADLESS that routes the driver to a headless chrome instance maximized to display the entire view port.
What is the current behavior of scaffold?
does not support headless chrome
What should we change?
update runtype to support HEADLESS
update WebDriverManager to create a headless Chrome browser with a overly large viewport
Why?
provides a mechanism for quick execution of automation
0 not meant for validation of the AUT, rather its a quick validation that the automation is functional and is meant to be used by developers doing a quick pre-commit check.
What are the risks?
none
Are there any alternatives?
Headless Firefox
A/C
assuming user has chromedriver installed, passing in HEADLESS will
create a headless version of Chrome
maximize the viewoport of the headless browser to be HUGE
this avoids any need to scroll to elements and what not (meant for quick verification)
Summary
Support a special run-type of HEADLESS that routes the driver to a headless chrome instance maximized to display the entire view port.
What is the current behavior of scaffold?
does not support headless chrome
What should we change?
update runtype to support HEADLESS
update WebDriverManager to create a headless Chrome browser with a overly large viewport
Why?
provides a mechanism for quick execution of automation 0 not meant for validation of the AUT, rather its a quick validation that the automation is functional and is meant to be used by developers doing a quick pre-commit check.
What are the risks?
none
Are there any alternatives?
Headless Firefox
A/C