Eric Wilhelm wrote:
But you didn't succeed because something's wrong and thus on the way out you must mention to the poor user what that might be. I suppose if we had a leave() function, you could get something like 'warn "can't install without ..."; exit 0' from 'leave "can't install without ..."', but we don't because a successful program doesn't have anything to say because there's nothing wrong.
I'm not sure. A synthetic example here would be some config parser that uses various XML parsers internally. Say the user doesn't have a reasonably fast XML parser installed but the slowest module possible. The config parser might use that one as a fallback and still work correctly (so technically the tests succeeded) but it might be so abysmally slow as to warant a warning to the user on exit.
So even on success (technical correctness), you might want to warn the user about the possible problems with his/her setup without failing the tests.
LG Rene
