As we write more and more stories, we obviously accumulate a growing number
of annotated step methods (currently we have ~350). I'm wondering what do
people do to more easily catalog the existing step methods so they don't
duplicate steps as well as ensure they're taking advantage of the steps
the
Chad - We're annotating our Step classes with @WeldStep
from org.jbehave.core.annotations.weld.WeldStep;
On Wed, Aug 20, 2014 at 2:23 PM, Chad Wilson wrote:
> Hello all,
>
> I'm not sure if I'm missing something here. According to the
> documentation in order to register Step class instances,
I don't want to skip the entire scenario, just one step.
On Tue, Jun 10, 2014 at 9:26 AM, Mauro Talevi
wrote:
> Annotate the scenario with a meta property, eg @skip, and set meta filter
> -skip.
>
> > On 10 Jun 2014, at 16:59, Frank Pedroza wrote:
> >
> > Is
Is it possible to skip single steps of a given story/scenario? I don't
think it is, but I'm wondering if there is a recommended approach. I have
a story with multiple scenarios and most of the scenarios can be fully
automated. However one of my scenarios has a few steps that really make
more sen
The entry point for our test runs looks something like the following:
@RunWith(WeldAnnotatedEmbedderRunner.class)
@Configure()
@UsingEmbedder(embedder = Embedder.class,
verboseFailures = true,
generateViewAfterStories = true,
ignoreFailureInStories = tr
