open-nomad/e2e
2019-01-28 11:18:59 -08:00
..
affinities e2e: add tests for nomad driver upgrade path 2019-01-17 23:32:45 -05:00
cli
consul Moved in place upgrade canary test over to new e2e framework 2019-01-27 20:15:35 -06:00
consultemplate Fix double restart counting for templates 2019-01-25 15:38:13 -08:00
e2eutil Apply suggestions from code review 2019-01-23 14:09:49 -05:00
example
framework Basic consul registration e2e 2019-01-26 10:58:25 -06:00
migrations
nomad09upgrade make nomad upgrade e2e build on non linux 2019-01-28 11:18:59 -08:00
rescheduling
spread e2e: add tests for nomad driver upgrade path 2019-01-17 23:32:45 -05:00
taskevents e2e: add tests for nomad driver upgrade path 2019-01-17 23:32:45 -05:00
terraform update to Consul 1.4.0 for e2e tests 2019-01-24 09:52:15 -06:00
vault fix iops bug and increase test matrix coverage 2018-12-11 15:28:21 -08:00
e2e.go
e2e_test.go Basic consul registration e2e 2019-01-26 10:58:25 -06:00
README.md Update README.md 2019-01-03 16:15:59 -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 Nomad 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