|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
|
|
Question off webtest canoo
Hi.
How to continue running step when previous step fails Thank. _______________________________________________ WebTest mailing list WebTest@... http://lists.canoo.com/mailman/listinfo/webtest |
|
|
Re: Question off webtest canooSee the config element, you must set the haltonfailure attribute appropriately. |
|
|
Re: Question off webtest canooI am not sure but I think the haltonfailure/haltonerror attributes are related to the "webtest" task not the "steps" task. If you are running a test with multiple checking in a page and you want to check everything without stoping on the first failure I don't think this will solve your issue. There is another thread that shows a solution for telling webtest to continue with next step when one step fails
<http://lists.canoo.com/pipermail/webtest/2009q2/012345.html>
Thanks, Hernan 2009/8/27 A Vander <avander_be@...>
|
|
|
Re: Question off webtest canooHi,
why do you want to continue if a failure occurs? Is it a failure or isn't it a failure? Cheers, Marc. -- Web: http://www.efficient-webtesting.com Blog: http://mguillem.wordpress.com Jose Antonio Avila Flores wrote: > Hi. > > How to continue running step when previous step fails > > Thank. > > > Jose Antonio Avila > javila@... <mailto:javila@...> > > > _______________________________________________ WebTest mailing list > WebTest@... http://lists.canoo.com/mailman/listinfo/webtest _______________________________________________ WebTest mailing list WebTest@... http://lists.canoo.com/mailman/listinfo/webtest |
|
|
Re: Question off webtest canooI think this depends on how you design your test case.
I think therer are at least two reason why I would like that: 1) Because of failure severity Something that it's not expected but it's something "blocker" (you want to keep testing) and some other failures that if that steps fails the you can't continue testing the next steps. (But this depends on how your test cases are designed. ) Example to ilustrate that //pseudocode testSmokeTest(){ Homepage.goto(context) Homepage.smokeTest() ---> (When I see the report I just want to be see the failures according to the severity) Homepage.clickCategoryLink(15) Listing.smokeTest() ----> } 2)Because of time spent on executions and analysis Let's suppose you have a Page composed of modules Homepage ->Module A ->Module B Module A is composed by a list of links, some links should have some condition according to the context related to the Homepage you are testing. So in some cases some links show have de "rel=nofollow" attribute for SEO reasons. This attribute is a dynamic and depends on the context of the page. So I would like to create a Class Homepage with the page logic a Class Module A with the module logic on Module A a have a method that is in charged of testing the nofollowAttributes of the complete module (each link) So once you create your ui model you can create a test like this //pseudocode testNoFollows(){ Homepage.goto(context) Homepage.moduleA.testNoFollows() } It's very explicit and easy to understand what you are testing. And what your are expecting is not to stop the execution on the first failure. You would like to see all the links that are failing. This way you run it once and then you analyse. You fix all the failures and then you run it again. The oposite of this is running it once, detect one error, fix that error, then running it another time fix it the second error, etc. It takes more time. Thanks, Hernan 2009/9/4 Marc Guillemot <mguillemot@...> Hi, |
| Free embeddable forum powered by Nabble | Forum Help |