let's start making it clearer (Paul, your explaination is interesting but not deterministic ;-()
What should be thrown when: - step has invalid parameters - step "context" is not present (ex: no current page for a step working on a page) - http error code is received - JavaScript error occured - in a verification, the actual value and the expected one differ Which of these cases should be "catched" by a wrapping <not>? I think that we should make at least a distinction between invalid parameters and the other cases (invalid parameters can be compared to a compilation error in junit). I don't have any problem to put all the other cases in the same category. Like Denis, I think that the invalid parameters case should not be catched by a <not>. Marc. _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
