#2 ctl:fail Processing

[Jeremy Parr-Pearson]

After a ctl:fail is processed (on a failure) the rest
of the current test is still run. It would be nice to
have the thread stop execution of the current test (or
have another ctl element that would do such,
i.e. "ctl:break") so that the rest of the test is not
executed if a ctl:fail is encountered.

This may not be desired for all situations, but for
some tests if the first part of the test fails there
is usually no need to proceed with the rest of the
test.

[Jeremy Parr-Pearson]

Logged In: YES
user_id=1578174

When a fail element is used it should skip the rest of the tests in that scope (or adjustable scope, by adding
a "scope" attribute). This way tests that are known to fail as well do not have to be run and the skipped status
can be logged.

As well, it would be useful to have a "message" attribute so that the reason for failing can be logged and output
to the screen.

i.e. (where scope of 1 is immediate node, and 2 includes the parent node as well - or some other convention)
<ctl:fail message="this test failed for this reason..." scope="1"/>

[luisBermudez]

Need to check if this is still an issue.