Skip to content

First pass at integration tests#273

Merged
paulbellamy merged 3 commits intoweaveworks:masterfrom
paulbellamy:integration-tests
Jul 3, 2015
Merged

First pass at integration tests#273
paulbellamy merged 3 commits intoweaveworks:masterfrom
paulbellamy:integration-tests

Conversation

@paulbellamy
Copy link
Contributor

Will fix #79.

Just adds a basic test for now. If people like this approach, I'll add another couple tests to this PR.

Depends on these changes being merged first, into the weave repo.

The setup.sh script in here will go get github.com/weaveworks/weave, for our working copy, and uses a few of the test helpers from there, to avoid duplicating. We considered having a separate repo for the integration test helpers, but didn't want to manage another repo.

Having separate vagrant files in here is a bit messy, potentially, so am open to suggestions on that, also.

Also, need to set these up to run on circle.

@paulbellamy paulbellamy force-pushed the integration-tests branch 2 times, most recently from effb291 to e4d63e2 Compare June 23, 2015 11:15
@tomwilkie
Copy link
Contributor

  • after discussion we decided we don't need the vagrant file as all prs are run through circle.

@tomwilkie
Copy link
Contributor

this will break scheduling as its not namespaced per repo. Could either disable it, namespace it, or add prefix to all the tests.

This comment was marked as abuse.

@paulbellamy paulbellamy assigned paulbellamy and unassigned tomwilkie Jun 23, 2015
@paulbellamy paulbellamy force-pushed the integration-tests branch 2 times, most recently from 65b8f3f to 04da157 Compare June 23, 2015 13:18
@paulbellamy
Copy link
Contributor Author

Won't running these on PRs have the same issue as on the weave repo (exposing gce credentials)?

@paulbellamy paulbellamy force-pushed the integration-tests branch 3 times, most recently from 6565e79 to a6e745a Compare June 23, 2015 13:58
@tomwilkie
Copy link
Contributor

It won't expose the keys if you put them in a variable in the circle ui (as opposed to checked in). This is how we do it on weave.

And Peter & David push to branched on weaveworks/scope, so the tests will run fine there.

@paulbellamy paulbellamy force-pushed the integration-tests branch 5 times, most recently from 9992f19 to dde9a40 Compare June 24, 2015 12:22
@paulbellamy
Copy link
Contributor Author

Just has one basic test for now. Needs more added...

Will skip integration tests on forked PRs (i.e. if there is no $SECRET_PASSWORD), but will run them on main-repo PRs.

@paulbellamy
Copy link
Contributor Author

@tomwilkie could you please review the weave side of things, while doing this. It will need to be in a release before this will work. We could point the integration tests at weave/master until that point.

@paulbellamy paulbellamy assigned tomwilkie and unassigned paulbellamy Jun 24, 2015
@paulbellamy paulbellamy force-pushed the integration-tests branch 5 times, most recently from 111fcb8 to 6f94001 Compare June 29, 2015 13:06
Integration tests are only run on circle. They checkout the weave
project, and use test helpers from there.

There are just a few basic tests for now, to confirm it works.
@paulbellamy paulbellamy changed the title Work in Progress -- First pass at integration tests First pass at integration tests Jun 30, 2015
circle.yml Outdated

This comment was marked as abuse.

@tomwilkie
Copy link
Contributor

1 comment otherwise LGTM

check before each integration test line is a bit ugly. Can combine them
into one step, but then you don't get metrics on how long each step
takes (in circle).
paulbellamy added a commit that referenced this pull request Jul 3, 2015
@paulbellamy paulbellamy merged commit 08f62aa into weaveworks:master Jul 3, 2015
@paulbellamy paulbellamy deleted the integration-tests branch July 3, 2015 08:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Integration tests

2 participants