Provide a simple facility to support T2's messages.
T2's Messages
Messages are printed to an output stream (the console or a log file;
should be configurable at the test engine setup). Classes that are
still in development may still print messages to console only; but
when they mature they should print to a seletable logging stream.
Different kind of messages produced by a T2 test engine:
- REPORT. The report produced by the engine. This may include
failures found in the target it is testing.
- PROBLEM. The test engine discovers some problem, e.g. in the
target it is testing. However it is not serious; the engine can
continue functioning.
Action: the engine prints a WARNING message and continues.
- INCOMPLETENESS. The test engine discovers that the target it is
testing has some aspect that is beyond the engine's capability.
Action: the engine prints an INCOMPLETENESS message and exits by
throwing a {@link U2.T2.Msg.T2Error T2Error}.
- ABORT. The test engine discovers a serious problem, as such
that it cannot safely continue its operation. The problem may be in
the target it is testing, or the engine was not properly setup. It
could also be a bug in the engine itself.
Action: the engine prints an ABORT message and exits by throwing a
{@link U2.T2.Msg.T2Error T2Error}.
- BUG. The test engine is in an unsafe state and positively
identifies that this is due to a bug in itself.
Action: the engine prints an BUG message and exits by throwing a
{@link U2.T2.Msg.T2Error T2Error}.
- DEVEL_WARNING. Message left by T2's developers to mark that
features which are still incomplete. When the engine stumbles on such
a feature, the message is printed.
Action: the engine prints an DEVEL_WARNING message and exits by
throwing a {@link U2.T2.Msg.T2Error T2Error}.
|