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. -- Web: http://www.efficient-webtesting.com Blog: http://mguillem.wordpress.com Linda de Boer wrote: > John Spann wrote: >> Hi Linda, >> >> Looking at your example from earlier, I don't see two webtests Here >> is what you originally setnt >> >> <project default="test"> >> <target name="test"> >> <webtest name="my simple Test"> >> &goToSite; >> >> <clickLink label="Home"/> >> <verifyText >> text = "Our primary goal is xto provide" >> description = "Display of middle of paragraph" >> /> >> >> <clickLink label="Services"/> >> <verifyText >> text = "Webpage design and development" >> description = "Check text on Services page" >> /> >> </webtest> >> </target> >> </project> >> >> Try the following instead: >> >> <project default="test"> >> <target name="test"> >> <webtest name="my simple Test"> >> &goToSite; >> >> <clickLink label="Home"/> >> <verifyText >> text = "Our primary goal is xto provide" >> description = "Display of middle of paragraph" >> /> >> </webtest> >> >> <webtest name="my simple Test"> >> &goToSite; >> <clickLink label="Services"/> >> <verifyText >> text = "Webpage design and development" >> description = "Check text on Services page" >> /> >> </webtest> >> </target> >> </project> >> >> Once a step within a <webtest> tag fails, none of the other steps are >> processed. You can define multiple <webtest> tags within a project. >> > G'day > > Yes, you are quite right, the previous version is out of date, it did > not contain two webtests. I had done some reading and added the two > webtests as that seemed the way I was to do it, then got it to proceed > to the next step. But did not want to redo the invoke. Currently as it > sits I have: > > <!DOCTYPE project SYSTEM "../dtd/Project.dtd"> > <project default="test"> > <target name="test"> > > <webtest name="check out home"> > <config > basepath="mypath" > haltonfailure="false" > haltonerror="false" > > </config> > <steps> > &goToSite; > &menu_home; > </steps> > </webtest> > <webtest name="check out services"> > <config > basepath="mypath" > haltonfailure="false" > haltonerror="false" > > </config> > <steps> > &goToSite; > &menu_services; > </steps> > </webtest> > > </target> > </project> > > > The test cases are simple verifyText, the "&goToSite" is just the invoke > and verifyTitle. Using the above, both pass. I'd like to be able to > leave any subsequent &goToSite's off. I realize that it may be necessary > so that each test case has a fresh start, however there are situations > where you want to keep going, ie; submenus, following links etc. > > Amy, I did read about the <not> and may have misunderstood it's purpose. > I do not expect the first test to fail, I do not want it to fail unless > it really is wrong. Am I taking the documentation wrong? Clarification > would be most welcome. > > Thank very much folks.....;-) > -- > ldb _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
