Hi Linda, I think you misunderstood Marc's question. He is asking why you are trying to combine the two tests into 1. Do you really need to avoid calling &goToSite; twice? Creating two tests does not have the same overhead as opening two "real" browsers. What Marc is trying to say is the overhead of having two tests and calling &goToSite; twice should be minimal.
The problem with having a single webtest continue running test steps if a step fails is you usually can't continue. Each webtest is a sequence of steps that must be executed in a specific order and a failed step leaves you in an inconsistent state. Clicking a link brings you to a new page. If that link could not be clicked or the page could not be loaded, all steps following the <clickLink> most likely won't work and most certainly won't be executed on the page you intended them to be executed on. I suggest you create macrodefs (preferred - see the definitions folder created by the sample project) or entities (like &goToSite;, although these become harder to maintain and reuse over time) for frequently used flows. That way you can write the sequence of steps to get to a particular page once, then write multiple tests for that page. Also, if you are trying to test validity of links on a particular page, you may want to try the verifyLinks step: <http://webtest.canoo.com/webtest/manual/verifyLinks.html>. Cheers, John Spann | Associate Software Engineer Citrix Online Division Citrix Systems, Inc. 6500 Hollister Avenue Goleta, CA 93117 USA www.citrix.com Phone: 805.690.3489 Cell: 805.729.0008 Email: [email protected] ________________________________ From: Linda de Boer <[email protected]> Reply-To: <[email protected]>, Linda de Boer <[email protected]> Date: Wed, 29 Apr 2009 05:45:52 -0700 To: <[email protected]> Subject: Re: [Webtest] Re: Continuing tests after a step failure Marc Guillemot wrote: > Hi Linda, > > is it that important to avoid the &goToSite? WebTest doesn't have the > long startup problems of tools driving a "real" browser what allows to > easily have independent tests. > > Cheers, > Marc. G'day Thanks for the advice. I must admit I am missing a point from it. What is the downside of the &goToSite? I use it because when I want to test each "top level" menu item, I start with a new access to the site, and didn't want it in several spots in case I needed to change the url or something later. So I might go to the site, then check if "Home" is working", then reload the site using the &goToSite and now test "Services" and any submenu items under it. Am I abusing webtest?..;-) Thanks very much.... -- ldb _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
