@satnam6502 @brendandburns

I'd rather move away from a monolithic test file into distinct files and
binaries that can be reasoned about somewhat independently. This would
need to be driven by a framework that ensures the cluster is up and
sanitized between tests.

On Wed, Jan 14, 2015 at 4:15 PM, Eric Tune notifications@github.com wrote:

Reopened #3490
#3490.

Reply to this email directly or view it on GitHub
#3490 (comment)
.

Agreed, but I think that's even longer term and not a contradictory goal.

Linking relevant other thread: #3447 (comment)

I am about to submit and update to my PR with all the Go tests split into
separate files now belonging to a package test/e2e.
This is still driven by cmd/e2e/e2e.go -- but in the following PRs we
should remove cmd/e2e/e2e.go and call these tests directly from hack/e2e.go
But I thought it made sense to split this into steps.

S

On Wed, Jan 14, 2015 at 4:32 PM, Zach Loafman notifications@github.com
wrote:

Linking relevant other thread: #3447 (comment)
#3447 (comment)

—
Reply to this email directly or view it on GitHub
#3490 (comment)
.

Snazzy! I should get hopped up on DayQuil more often!

@thockin : I think it is fine (in fact, preferable) to have all the Go e2e tests in one package as long as we have a way to conditionally execute each test. Which is a feature that I (or someone else) will add shortly to our Go e2e tests.

Also, I am trying to chip away at the e2e tests with a view to getting them into shape for use with the Go testing framework -- also suggested by @filbranden -- which would be a great improvement. This would have all the tests in a single package.

Is this monolithic issue still needed?

@zmerlynn @satnam6502 @filbranden

Closing as obsolete.