On Thu, Oct 23, 2008 at 11:20 PM, Michael Latta <[EMAIL PROTECTED]> wrote: > That works when running one at a time. When I want to run all my specs how > do I ensure the requires are applied to the appropriate features? It is not > all my stories, only a subset that are dual-purposed. Do I need to have > directories for those that can be run dual mode and those that are not, and > then have a script that runs the 3 cases? >
You have to run once for each "environment". So if you have say selenium and rails, you'll have to run all features that use selenium in one run and those that use rails in another. (Of course you can have overlap - some features that include run in both runs) Aslak > Michael > > > On Oct 23, 2008, at 11:49 AM, Zach Dennis wrote: > >> On Thu, Oct 23, 2008 at 1:20 PM, Michael Latta <[EMAIL PROTECTED]> wrote: >>> >>> It appears we were too clever, but I think this would be a reasonable use >>> of >>> stories. >>> >>> We tried to have a story file run with 2 different sets of steps to use >>> the >>> same story against both the UI using selenium and against the server API >>> using regular get/put/post. This way we could spec the server API and >>> the >>> UI while ensuring they are in sync for the scenario in question. But >>> stories get confused when there are stories or scenarios with the same >>> names. >>> >>> Does Cucumber deal with this any better than the story runner? Given >>> that >>> it searches for steps rather than having them declared, I would think you >>> can not share story files for different steps? >> >> You can do this, you'd just put the steps in different directories and >> tell cucumber to require the files in one directory for one run, and >> another for another run. ie: >> >> cucumber --require features/steps/selenium/ features/ >> AND >> cucumber --require features/steps/normal/ features/ >> >> -- >> Zach Dennis >> http://www.continuousthinking.com >> http://www.mutuallyhuman.com >> _______________________________________________ >> rspec-users mailing list >> rspec-users@rubyforge.org >> http://rubyforge.org/mailman/listinfo/rspec-users > > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users > _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
