The examples form an integral part of the project, ensuring the correct
behaviour of the releasable modules. They're not just examples, but
more akin to acceptance/integration tests.
If you are looking for examples that are not connected to the code, then
the jbehave-tutorial is place to
Somehow GivenStories does not work as expected in the 4.x branch. It is not
executed.
But when I use jbehave-core 3.9, then the GivenStories are executed.
See my example below. It is in German, I changed the story language.
GivenStories is VorgegebeneStories.
Maybe this information is enough to
I discovered that I can run a completely empty story. It contains nothing,
no narrative, no scenarios and no steps, nothing.
If I run it then no failure is shown.
Why is so much allowed when writing a story? Why is it not required that a
story has at least one step and that there is no scenario
Hi Hans,
the issue has been noted and fixed. The given stories were only
executed at scenario level but not at story level.
A new 4.0-beta-7 is being released.
Cheers
On 02/05/2014 11:36, Hans Schwäbli wrote:
Somehow GivenStories does not work as expected in the 4.x branch. It
is not
The unbearable emptiness of being :-)
The idea is to try and encourage partial story writing. E.g. once
might only write a description and a narrative, but not yet have any
scenarios to add.
If one write a scenario though, at least one step must be present.
We could add a warning saying
org.jbehave.core.reporters.StoryReporter contains a scenarioMeta(Meta meta)
method.
But it does not contain a method like storyMeta(Meta meta).
I need to access the Meta information for the story in the StoryReporter.
Was it forgotton to add that method into StoryReporter or did I overlook
The meta at story level is always merged with the meta at scenario level.
This is why only the resulting meta is reported.
We could add the reporting of story level meta, but what is your use-case?
On 02/05/2014 14:22, Hans Schwäbli wrote:
org.jbehave.core.reporters.StoryReporter contains a
Ah, okay, I see. Then I think I can do what I want with it.
I want to use a meta information which represents a link to the test case
in HP Quality Center.
Meta:
@qc-testcase Root/Test/Test-Testset/TesA
In StoryReporter.afterStory(...) I want to upload the test result into HP
Quality Center at
