Set up a better integration testing harness.

[mattmoor]

Manually inspecting the output as currently described in the README.md is error-prone and highly undesirable. These should be harnessed into some level of testing that can be orchestrated by Travis or some other CI setup (potentially thru Bazel, e.g. sh_test)

We should run the appropriate configuration against each "builder" (currently Google vs. Cluster).

@imjasonh FYI as I know this is a sore spot.

[mattmoor]

@bobcatfish FYI. I'd like this to track your investigation here which I think covers integration testing.

[bobcatfish]

thanks @mattmoor ! I'm planning to tackle knative/serving#253 for milestone 4 FYI. Also @adrcunha is working on automation for the conformance tests which could maybe be reused for these tests?

[bobcatfish]

I'm planning to tackle knative/serving#253 for milestone 4 FYI

But I tagged it with M3 ... 😅 I am the worst

[adrcunha]

Test orchestration is now handled by Prow (#106), and the automatic output checking is tracked by #101. Whether the shell script should be rewritten as a go test or not, or handle other cases, is a future improvement.