I think that it is gooing too far and that we should avoid to break current behavior.
Currently we have (in the selftests themself) things like: <not> <invoke description="some wrong url" url="xxx"/> </not> It should continue to work. This means that only bad parameters of step nested in a <not> should make the <not> fail (and of course when a step nested in not is successfull). When I've asked this question, my intention was to bring more information in the report, particularly the original exception of a JS error (containing original code snippet). Currently we don't write the exception stack trace in the report for StepFailedException but only for StepExecutionException. If we aren't able to clarify the exceptions point, it will be enough for me to add the stack trace of StepFailedException in the reports too (even if it is not really interesting for "normally failed" steps). Marc. _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
