1. Yes - you can specify as many stories as you want as given stories. Just provide a comma-separated list. 2. Yes - the stories are run in the sequence. By default, multiple lookups (e.g. **/*.story) are ordered in alphabetical order of the story name or path, but you can either sort them in the order you prefer or explicity specify the story path sequence.
Best practice is not to depend on order, but to use given stories. Cheers On 21/03/2011 11:08, Arpit Sakhi wrote: > > Hello, > > > > I have a query regarding running multiple stories as a sequence. Let > me explain the scenario for which I am trying to find the solution. > > > > Lets say I have a Assignment story(Assignment.story) which depends on > login story(login.story). In assignment story I am using login.story > as given story so once I execute assignment.story it will first run > the login story to log into application and then performs a operation > of assigning some report to other user. > > > > Now I have another story (myreprot.story) which will check for reports > (assigned in assignment.story) for particular user . For example in > normal application admin creates tickets and assign to respective > person and once that respective person logs in, he will get all his > assigned tickets in system. As per above example I want to verify that > assigned reports by logging in with assignee credentials. So > myreport.story will again have login.story as givenstory but I want to > execute assignment.story too before the myreport.story. > > > > I think the solution lies in below 2 queries -- > > 1. Can we specify the multiple stories in given story? > > 2. Can we run multiple stories in sequence by giving the list of > stories in storyfinder? > > > > Thanks in Advance > > Arpit > > > > > > DISCLAIMER ========== This e-mail may contain privileged and > confidential information which is the property of Persistent Systems > Ltd. It is intended only for the use of the individual or entity to > which it is addressed. If you are not the intended recipient, you are > not authorized to read, retain, copy, print, distribute or use this > message. If you have received this communication in error, please > notify the sender and delete all copies of this message. Persistent > Systems Ltd. does not accept any liability for virus infected mails. >
