search

BD2KGenomics / ga4gh-integration-deprecated

Tracking for ga4gh-integration projects
1 stars 2 forks source link

Cross-repository testing strategy #41

Open dcolligan opened 7 years ago

dcolligan commented 7 years ago

Once we have separated client, server, schemas, etc. into their own repositories, we need to ensure that each repositories' tests are sufficient to ensure that it correctly works with the current code of all other repositories.

dcolligan commented 7 years ago

Going to start development here: https://github.com/dcolligan/testbed

Eventually we want to put this into a ga4gh repo, however.

david4096 commented 7 years ago

I think that we can come up with a continuous integration system that doesn't require another repository. Think about importing the server for the schema tests, perhaps?

dcolligan commented 7 years ago

What CI platform are we going to use besides Travis?

I don't want to burden individual repositories with integration testing from other repositories. I'd rather have each repository have its own tests and then do the integration testing elsewhere. That seems easier to reason about, and has the advantage of only requiring us to change one repo when our dependencies, etc. change.

dcolligan commented 7 years ago

Looks like there is no magic in github to support something like this:

http://eng.rightscale.com/2015/04/27/dependent-builds-in-travis.html https://github.com/travis-ci/travis-ci/issues/249