Story printing without executing the code

[Jaimme]

I have large number of story files that take many hours to run. What I
need is a txtstory type of output to take to the business for review,
but I don't want the actual test code to get executed...meaning I
don't have to wait a couple days to get my txtstory output. Is there a
way to do this?

[Richard Vowles]

Not at the moment it appears. The StoryKeywords and SpecificationKeywords always execute the story as long as ignore isn't requested, which isn't really what you want. I expect you need a command line flag that just iterates over all the stories and returns PENDING (or something else) for each of the items in the story?

I would create an Issue on the issue tracker if I were you and link back to it here - then we can talk about it on the dev list.

--
---
Richard Vowles,
Grails, Groovy, Java
Consistency is the last refuge of the unimaginative - Oscar Wilde
ph: +64275467747, linkedin, skype:rvowles
get 2Gb shared disk space in the cloud - Dropbox, its incredibly useful! - http://tinyurl.com/cmcceh
podcast: http://www.illegalargument.com

[Andy Glover]

I agree- this sounds like a great feature! 

Sent from my iPhone

[Andy]

FYI- this is now issue 165 -- thank you for the great idea!
http://code.google.com/p/easyb/issues/detail?id=165

On Oct 9, 5:50 pm, Andy Glover <ajglo...@gmail.com> wrote:
> I agree- this sounds like a great feature!
>
> Sent from my iPhone
>

> On Oct 9, 2009, at 5:09 PM, Richard Vowles <richard.vow...@gmail.com>  

> wrote:
>
> > Not at the moment it appears. The StoryKeywords and  
> > SpecificationKeywords always execute the story as long as ignore  
> > isn't requested, which isn't really what you want. I expect you need  
> > a command line flag that just iterates over all the stories and  
> > returns PENDING (or something else) for each of the items in the  
> > story?
>
> > I would create an Issue on the issue tracker if I were you and link  
> > back to it here - then we can talk about it on the dev list.
>

> > On Sat, Oct 10, 2009 at 7:17 AM, Jaimme <jaimmehenn...@gmail.com>  

[Andy]

Hi Jaimme! This feature has been added to the trunk of easyb -- if
you'd like to start using it now, just download and build the source.
There is a new flag (-ne) that can be passed in via the command line
or via Ant with the noExecute flag (I have yet to add this to maven --
are there any maven experts out there?! :)) -- with this flag, all
stories (not specifications at this point) are not executed but a
report is generated (there isn't a status associated with the
scenarios, btw).

Let me know if this is what you were looking for!

[Jaimme]

Thanks for adding this feature! The only concern I have is that both
the html and xml reports show the scenarios as successes instead of
pending, I'm assuming this is what you meant by there isn't a status
associated with the scenarios.
Otherwise txtstory, html and xml all work great!
Jaimme

[Andy Glover]

You think they should say pending?

Sent from my iPhone

[Jaimme]

I think it is less misleading than success or failure. Ignored might
tell the business not to review those tests. Maybe a new status like
'in-review' or something to indicate the no execute flag was on.

On Nov 6, 9:18 am, Andy Glover <ajglo...@gmail.com> wrote:
> You think they should say pending?
>
> Sent from my iPhone
>

[Andy]

I've added a new status dubbed "in review"; thus, when the no execute
feature is used, the prelude to a report states x number of "scenarios
in review" rather than executed successfully. This is feature is
checked in and in the tip of SVN.