Its will be fine if we have a <maybe> type step in WebTest. But if its like in a particular project there is nightly build system. So the developer will be like only concerned if any high severity verifications are passing and well and not affected By the changes done to the code or to the application.

One more point will be like it will be more flexible as the user might specify before running the WebTest scripts what type of checks should be checked like only to check if medium and high priority checks are passed or only high priority checks are passed or all priority checks have to be passed.

There is also some JIRA issue as I created my account but was not able to login it was saying password incorrect. Then I tried for the forgot password link but I didn't got the mail of my password.

Thanks & Regards Vikram Shitole 'The future belongs to those who believe in the beauty of their dreams'

From: "Dierk Koenig" <dier...@canoo.com> To: <webt...@lists.canoo.com> Subject: RE: [Webtest] To Set Priority to each step Date: Tue, 1 Mar 2005 10:26:07 +0100 Reply-To: webt...@lists.canoo.com

I've heard similar requests recently.

The <maybe> solution is the best I can currently think of.

I would like to add that I understand the whish for such a step, but that I'm not convinced by the idea of testing something that one would allow to fail. What is the point about a verification that is equally ok whether it fails or not?

Vikram: could you open a feature request for this in our JIRA?

cheers Mittie

MASTEK "Making a valuable difference" Mastek in NASSCOM's 'India Top 20' Software Service Exporters List. In the US, we're called MAJESCO