Headless Chrome for Testing

This is an opinionated image for testing apps in chrome. It ships with a couple of tools and libraries found in the next section. It facilitates the builder pattern so the final included tools differ from the build stage.

Tools and Libraries

PACK_CORE

• curl
• build-essential
• chrome
• chromedriver

How to use this

The image comes with a Makefile that has everything abstracted away for you to easily customize it.

$ make make NODE_VERSION=13.10.1 ALPINE_VERSION=3.11 build push

Available VARS

CHROME_VERSION=80.0.3987.106
REGISTRY=${REGISTRY:-ORGANIZATION/headless-chrome}
VCS_URL=${VCS_URL:-https://THE_REPO_URL}

Optional Setup

If you are into some tooling for keeping commit-messages clean and want to keep an automated CHANGELOG.md, feel free to make init ;).

It'll install the node_modules:

• standard-version,
• husky
• commit-lint

To make this work you need to have NODE.js installed.

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style.

1. Fork it
2. Create your feature branch (git checkout -b feature/my-cool-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin feature/my-new-feature)
5. Create new Pull Request

License

Copyright (c) 2020 Territory Embrace - Talent Platforms.