open-nomad/e2e
2019-01-03 14:02:02 -06:00
..
affinities new e2e test for spread, and refactor affinity tests to share util methods 2018-12-19 21:25:32 -06:00
cli fix panic 2018-09-18 13:02:03 -07:00
consul consul: support canary tags for services 2018-05-07 14:55:01 -05:00
e2eutil Increase alloc wait timeout in e2e test 2019-01-03 14:02:02 -06:00
example e2e/cli: fix formatting 2018-07-31 13:52:25 -04:00
framework new e2e test for spread, and refactor affinity tests to share util methods 2018-12-19 21:25:32 -06:00
migrations remove unnecessary test output print 2017-11-01 15:21:05 -05:00
rescheduling Add more end to end tests for progress deadline and fix flaky test 2018-06-05 17:25:28 -05:00
spread Clean up map update code 2018-12-20 15:12:48 -06:00
terraform Update README.md 2019-01-03 13:19:04 -06:00
vault fix iops bug and increase test matrix coverage 2018-12-11 15:28:21 -08:00
e2e.go e2e: skip e2e tests during normal go test runs 2018-07-31 12:42:36 -04:00
e2e_test.go Fix spread e2e test 2018-12-19 17:11:26 -06:00
README.md Update e2e readme 2019-01-03 13:24:58 -06:00

End to End Tests

This package contains integration tests.

The terraform folder has provisioning code to spin up a Nomad cluster on AWS. The tests work with the NOMAD_ADDR environment variable which can be set either to a local dev Nomad agent or a client on AWS.

Local Development

The workflow when developing end to end tests locally is to run the provisioning step described below once, and then run the tests as described below.

Provisioning

You'll need AWS credentials (AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY) to create the Nomad cluster. See the README for details. The number of servers and clients is configurable, as is the configuration file for each client and server.

Running

After completing the provisioning step above, you should see CLI output showing the IP addresses of Nomad client machines. To run the tests, set the NOMAD_ADDR variable to one of the client IPs.

$ NOMAD_ADDR=<> $NOMAD_E2E=1 go test -v