Closed 27Bslash6 closed 5 years ago
Tested it locally and works great :coffee:
My initial goal here has been to get the tests running/passing and in a merge-able state. They seem to have decayed a bit over time :)
In the follow volley of commits there I've added/resolved:
/etc/hosts
entry) https://github.com/greenpeace/planet4-docker-selenium-tests/pull/3/commits/d8f6164bf1f7b3c93b75b29f0bd4c25ce4a8ccd2tests/data/images
in the selenium test repo into the gallery https://github.com/greenpeace/planet4-docker-selenium-tests/pull/3/commits/d7e25f960592a68a329c1e2c4a790d20402179e1 https://github.com/greenpeace/planet4-docker-selenium-tests/pull/3/commits/0eeda6235418af07df9bc577a3b5a00d7166d09fAll the tests (16) that haven't been commented out just passed for the first time https://circleci.com/gh/greenpeace/planet4-docker-selenium-tests/56 :)
I would propose to merge https://github.com/greenpeace/planet4-selenium-tests/pull/12 first, then switch the configured tests branch back to master, then merge this one.
Dockerfile overhaul. Too many changes to detail.
Makefile integration - isolated common tasks to simple commands such as
make build
make run
make exec
make test
etc.Rudimentary CI integration, including running all tests against a stock install: this will require forthcoming rewrites to the test suite.
Gulpfile for monitoring changes to tests, and running tests only on the changed files.
Example cron daily job running tests - will require further configuration to properly run tests against k8s.p4/develop and dev.p4