Commit Graph

109 Commits (e998d6c2bc83385d98186a87e95a0f947e121ec1)

Author SHA1 Message Date
Brendan Burns c9657cad04 Merge pull request #4319 from justinsb/aws_fixes
Fixes to get AWS tests to run
2015-02-18 22:43:46 -08:00
Alex Robinson 94161a44ee Pass the GCE project, zone, and master name into e2e.go as flags. 2015-02-18 15:41:36 -08:00
Alex Robinson f946aa887b Migrate the certs.sh e2e test to ginkgo. Issue #4185. 2015-02-18 13:45:44 -08:00
Jeff Lowdermilk aa32f1b2ce Retry #4337: Make gce kubeconfig context include project 2015-02-13 13:31:50 -08:00
Justin Santa Barbara cf470f7da4 Fixes to get AWS tests to run
They don't pass (yet), but they at least run!
2015-02-11 15:58:33 -05:00
Justin Santa Barbara 8cbd97d8bd Default value for ${@}, otherwise nounset causes failure 2015-02-11 12:39:06 -05:00
Zach Loafman 134d332793 Move verbosity flag into driver.go, randomize specs
Before we get too many suites baked, I want to get spec randomization
in, just so no one accidentally thinks things flow from top to bottom.

The random seed is printed with every run:

Random Seed: 1423194521 - Will randomize all specs

and can be reproduced using --ginkgo.seed
2015-02-05 19:49:04 -08:00
Zach Loafman bace7593d0 Enable ginkgo.v (console output is missing spec without it) 2015-02-05 07:24:05 -08:00
Zach Loafman 688f96cd33 Run shell tests under Ginkgo, changing all reporting to JUnit
* Add a test/e2e/shell.go that slurps up everything in hack/e2e-suite
and runs it as a bash test, borrowing all the code from hack/e2e.go.

* Rip out all the crap in hack/e2e.go that deal with multiple tests

* Move hack/e2e-suite/goe2e.sh to hack/ginkgo-e2e.sh so that it
doesn't get slurped up.
2015-02-05 07:24:05 -08:00