NEW REQUIRMENT :- Call one Scenario from another Scenario

[viral shah]

Hi there,

I know in specflow we can able to run particular steps from one feature to another feature and so on. But i really feel like if we can able to implement the way that we can able to call whole scenario with its example data so it will be really good improvement . Is that something you can add into your development item ? I've gone through lots of online discussion forum and community and they all saying that it will some how depends upon the Framework you using but that is not realistic as we are following strict Rules for BDD. 

Let me know your views .

Thanks 

[Umair Chagani]

This is a bad idea. Each scenario should stand on its own. If you setup to do, it's best do isolate the setup only so you can do that in multiple scenarios.

--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[viral shah]

Hi uchagani,

well, i totally disagree with you. you are saying that each scenario should stand on its own then why are we able to re-use the steps ? if you look at the top level then,what i m asking is the same thing we already have . it is just a shorter approach i'm asking .

i will give you an example, lets say we do have to do more than 200 different transactions for all different types, now we have already implemented that . Now then thing is we are automating the back end part and of course feature file will be different but those back end stuff will be only able to happen with 200 front end transactions . Now you are saying that i should copy all the steps for all 200 transactions (scenarios) in those back end feature file which i dont think make sense at all.......... so rather than coping the steps we should just call those scenarios as a just one line code (like do this before execute back end scenarios ). I know we can use hooks but we can put everything in hooks.....

[viral shah]

Hi uchagani,

well, i totally disagree with you. you are saying that each scenario should stand on its own then why are we able to re-use the steps ? if you look at the top level then,what i m asking is the same thing we already have . it is just a shorter approach i'm asking .

i will give you an example, lets say we do have to do more than 200 different transactions for all different types, now we have already implemented that . Now then thing is we are automating the back end part and of course feature file will be different but those back end stuff will be only able to happen with 200 front end transactions . Now you are saying that i should copy all the steps for all 200 transactions (scenarios) in those back end feature file which i dont think make sense at all.......... so rather than coping the steps we should just call those scenarios as a just one line code (like do this before execute back end scenarios ). I know we can use hooks but we can put everything in hooks.....

On Tuesday, December 15, 2015 at 5:09:57 PM UTC+11, uchagani wrote: