Enhance 27 functional tests for travis

[grantmacken]

This is a rework or .travis.yml for issue #27 See last build on travis-ci

The following smoke tests are carried out on a running container instance of a freshly minted image The container is brought up with docker-composer

• [x] check eXist is starting with health status
• [x] a timeout wait until eXist can be reached on port 8080
• [x] after sleeping for 30 sec the health-check should register healthy

The following functional test checks are carried out on the first travis job stage

• [x] changing password with client.jar checks the ability to

  • invoke client.jar
    • change password
    • query db with new pass test: after changing password the is-dba() query call should return true

• [x] obtain running container eXist 'version' checks the ability to

  • invoke a http client (curl)
    • use GET to query the database test: the get-version() query, should match the version of the freshly minted built image

• [x] posting requests to rest endpoint url via CURL checks the ability to

  • invoke a http client (curl)
    • query the database by POSTing a query test: the list returned from a repo:list() query, should grep 'http://'
  • [x] manage config files check the ability to
    • copy a config file from container to local disk test: after copying conf.xml the file should exist locally

• [x] persist changed configuration items checks the abilty to

  • alter a config item in a config file on local disk,
  • copy the altered config file into containers config dir.
  • stop and start the container
  • view changed item taking effect in startup logs test: the startup log should show altered shutdown time

• [x] log to docker logs checks the abilty to

  • call log functions
  • view results in docker logs test: eXist log queries output should turn up in docker logs

The main aim was to add run-time functional tests, that tests what we have altered in eXist specifically for the container image

27 issue Items not covered in this pull request

• [ ] make sure that dashboard is accessible (based on experience healthcheck is not enough for this)
• [ ] Ideally we would check that no ERROR messages appear in the log after startup

[adamretter]

Wow quite comprehensive.

I wonder if it would be worth splitting this into install and script steps - https://docs.travis-ci.com/user/customizing-the-build/#the-build-lifecycle

Also, perhaps it is better to extract the shell scripts from .travis.yml into a separate shell script. With a separate shell script, we can then also run the tests locally, and we can easily check and validate any syntax errors.