There is no way to execute testing with an AWS_LAMDA against a docker container without selenium/standalone-chrome as a service. This is partially due to the fact that a remote url is required in order to execute the testing. Furthermore, it will only create a new instance of a RemoteWebDriver instead of a local web driver.
Expected
There are use cases where the AWS_LAMBDA will execute a handler against a docker container that includes chrome and chromedriver on the same container. We should have two different run types for a local and a remote AWS_LAMBDA execution.
Repro
Setup a spring profile that uses AWS_LAMDA as a run type without remote url
Bug
There is no way to execute testing with an AWS_LAMDA against a docker container without selenium/standalone-chrome as a service. This is partially due to the fact that a remote url is required in order to execute the testing. Furthermore, it will only create a new instance of a RemoteWebDriver instead of a local web driver.
Expected
There are use cases where the AWS_LAMBDA will execute a handler against a docker container that includes chrome and chromedriver on the same container. We should have two different run types for a local and a remote AWS_LAMBDA execution.
Repro