Add a pod update e2e test in go. Also adjust validation logic a little.

[brendandburns]

Not integrated into existing e2e yet.

[lavalamp]

Is the idea that the e2e tests will drive this?

[brendandburns]

Yeah, once this is, I'll add a script to the e2e suite to drive this binary.

(and eventually we'll tear down the e2e scripts in favor of this binary.)

[lavalamp]

I think--since you're starting a test framework here--that many of these functions should be put in a library. Is the plan one binary per e2e test, or all e2e tests in one binary?

[brendandburns]

All tests in one library. I can split it out into a library, if you really
prefer, but why, are we going to unit test the integration test? (I mean
we could, but...)

On Tue, Oct 14, 2014 at 10:07 PM, Daniel Smith notifications@github.com
wrote:

I think--since you're starting a test framework here--that many of these
functions should be put in a library. Is the plan one binary per e2e test,
or all e2e tests in one binary?

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

[lavalamp]

Don't have to do it for this change, but soon. Yes, we will have to unit test the test framework.

Also, need a system where each e2e test goes in its own file or something, this is already too long for a single file IMO. Would be cool if it could be set up like the set of integration tests that @smarterclayton started.

[brendandburns]

Ok, works for me, will take as a TODO. Can we merge this and then iterate?

Thanks!
--brendan

[lavalamp]

Sure, we can iterate.