Closed chiarng closed 2 years ago
Hi @chiarnglin is this issue still valid with headless browser capability in SD Headless Browser ? I Have yet to try but I can confirm in a week or so when I get some free time.
ATF headless browser solves this issue, difference being rather than the pipeline script initiating the docker engine call to run a container, the SN instance does it when no existing scheduled client test runner is detected upon execution of an ATF UI test.
Today, when ATF UI Tests run, they need a Scheduled Client Test Runner opened in a browser tab/window somewhere. This is annoying for automated pipelines, for obvious reasons. One way to address this would be to have a Scheduled Client Test Runner for the target instance running, either persistently or ephemerally (on-demand from pipeline build).
We could use https://github.com/chromedp/docker-headless-shell and provide another example yaml file.