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).
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.