Test() changes program flow

[dbaggerman]

The Test() function prevents Fatal() from calling os.Exit to terminate the process, as this would be undesirable when running a test suite.

However, not calling os.Exit means that functions that would normally abort with printer.Fatal instead continue running despite the error. This means that the behaviour of a function in testing may not match it's actual behaviour.

One solution may be to panic in testing rather than continuing, which will allow the test to check the panic occurred, and recover from it. Using a terminate callback which the test code can overwrite might be even more flexible.

[ojkelly]

panic and recover in the test, sounds like a better way to handle that.

You've covered the reason why Test() was added, so if we can handle this feature in a more idiomatic/stable way we should.

Do you mind making a PR?