Hi Brent,
this is an interesting use case. I've created two issues:
http://jira.codehaus.org/browse/JBEHAVE-1032 to make the MetaMatcher
injectable
http://jira.codehaus.org/browse/JBEHAVE-1033 to add JiraMetaMatcher in
jbehave-rest.
If you could provide a pull request for JBEHAVE-1033 it'd be most great!
Cheers
On 12/07/2014 00:51, Brent Barker wrote:
Great thank you for your response!
I'd like to avoid editing the MetaFilter class if I can. Making it
injectable would be a great feature to have. Using the
GroovyMetaMatcher is not working for me. I need to call a class in my
local repo, but the groovy script is not able to resolve the class.
I am trying to access Jira though Rest to see if a bug for the
scenario is closed or open, and skip or run the scenario depending on
that.
On Fri, Jul 11, 2014 at 12:21 AM, Mauro Talevi
<mauro.tal...@aquilonia.org <mailto:mauro.tal...@aquilonia.org>> wrote:
The recommended way is to implement your own MetaMatcher.
Currently, you need to extend createMetaMatcher(String) method in
MetaFilter although we could make it injectable.
Alternatively, use the GroovyMetaMatcher to invoke a groovy script
that will do you check.
Cheers
On 10/07/2014 19:49, Brent Barker wrote:
Hi everyone!
Is there a easy way to conditionally skip a story using a meta
tag? For example, I want to annotate my story with @bug
BUG-3333 and then check if that bug is still open or not. If
it is still open, skip the scenario/story.
Right now I am extending RegexStoryParser, calling
super.ParseStory to get the story object, then if the bug meta
property exists, I add the skip meta property to it.
Is there a better way to do this? I am not sure how to feed a
list of meta filters to the embedder, since I can not access
it from the story configuration where I have access to the
story object
Thanks
-Brent
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
