An example of this container being used for Angular:
# !/bin/bash
# the currenty testing entry point is via:
# ENTRYPOINT ["bash"]
# At the moment, it would be best to define
# a smoke test in a shell script for running
# within the CI/CD. Specifying a specific
# suite is beneficial as you can freely determine
# the tradeoff of quality and money (as CI/CD services
# such as CodeCommit are typically pay as you go)
#
# Our example smoke test in a `./test` shell script file
set -e
npm install
./node_modules/@angular/cli/bin/ng e2e --aot --prod
./node_modules/@angular/cli/bin/ng test --single-run
docker run -v $PWD/examples/angular-example:/protractor -w /protractor "$AUTHOR/$CONTAINER" ./test
Updates
A notorious issue with ChromeDriver is its frequency of updating - and rendering old webdrivers obsolete. I have a TravisCI Cron job re-build the Docker containers daily (and therefore pull in the latest webdrivers). In your personal use, it is advisable you update them often when it fails to run outside of any errors within a testing script.