We are at a point where we could start using docker for integration testing.
The closest we have to automated integration is ZipkinQueryServerFeatureTest, as this actually issues GET requests against a live http endpoint. We could look into harvesting this out as an executable spec, like Apiary Blueprint or Swagger Tests
We currently do "manual integration tests" in the following ways.
docker-compose up then bin/tracegen $DOCKER_IP
docker-compose up then click refresh until traces show up, then look at the details.
undocumented for docker run the mysql backend, then seed the dependencies tables. view in UI
Travis supports launching docker containers when in legacy mode. We should be able to run at least some of these scenarios automatically.
We are at a point where we could start using docker for integration testing.
The closest we have to automated integration is ZipkinQueryServerFeatureTest, as this actually issues GET requests against a live http endpoint. We could look into harvesting this out as an executable spec, like Apiary Blueprint or Swagger Tests
We currently do "manual integration tests" in the following ways.
docker-compose upthenbin/tracegen $DOCKER_IPdocker-compose upthen click refresh until traces show up, then look at the details.Travis supports launching docker containers when in legacy mode. We should be able to run at least some of these scenarios automatically.