Hi Paulo,
I agreed with Clemens...
In my opinion, reusing things, the way you always do with OO, not always
is a good thing when we start to think about User Stories.
I had this kind of problem in my transition from UseCase to Stories. We
had lots of use case diagrams in a tool and specification on ms word.
The first thing that we learned was that we shouldn't write our story as
it was a BASIC code with lots of GOTOs.(for people that remeber it ;-)
)... BDD emerge from a User necessity to understand well the
requirements...
Other thing that I could observe is that a Uml Usecase Include doesn't
fit well to a GivenStories... at least in our case, just feel ones was
mantained...
The we radically stopped to use UseCase as our capture requirements way,
with it's Alternative " Users Crazyer" Paths, and we started to use
Stories with scenarios and JBehave...
Now we have Stories that has ONLY ONE main path and Scenarios that are
variations inside the story context... it should be clear for our not
technical user and for the team. User should read it, understand it, and
sign it...
We still use GivenStories, but only when we dont need any variations on
the included story...
Ok... not reusing texts maybe let us with more texts files... may be,
but this texts could be at source control or on a wiki (being edited by
the user himself) where we can easy track changes...
And you have lots of way of reusing your Steps classes and others Java
classes using the Jbehave DI feature... It's very powerfull....
cheers
Cristiano
Clemens Wyss escreveu:
(in other words, the
step description would be repeated in many different stories).
why repeat? Say you have
AuthenticationSteps
RegistrationSteps
and
ApprovalSteps
then I would implement Given("I am authenticated as '<uid>' with password '<pw>'") in
AuthenticationSteps (because it "fits" there ;-) ) and re-use AuthenticationSteps (hence adding them
to the InstanceStepsFactory call) in all three stories. Hope this makes my point clear?
I was wondering if it would make sense to pass parameters in the
GivenStories inclusion.
Where should the parameters by applied?
- GivenStories implies that you can specifiy multiple stories
- what if the story has different scenarios?
----- Ursprüngliche Nachricht -----
Von: Paulo Sérgio Medeiros
Gesendet: 07.09.10 07:51 Uhr
An: [email protected]
Betreff: Re: [jbehave-user] Parametrizing stories
So, if I understood you correctly you are basically saying that I should not
use the GivenStories functionality in this case and reuse the authentication
steps code but not the authentication story description (in other words, the
step description would be repeated in many different stories).
Have I understood it correctly?
I was wondering if it would make sense to pass parameters in the
GivenStories inclusion. What do you think?
On Tue, Sep 7, 2010 at 2:40 AM, Clemens Wyss <[email protected]> wrote:
I would keep your authentication story (with its examples I guess?) as is
and create a convenience Given-step à la:
Given I am authenticated as '<uid>' with password '<pw>'
for request registration and request approval stories. Code reuse can be
made in the step implementation of Given("I am authenticated as '<uid>' with
password '<pw>'") from which you can call the method(s) of the
authentication story. You could (possibly should) implement this convenience
step in the AuthenticationSteps class and include it in the registration and
request approval stories.
Regards
Clemens
----- Ursprüngliche Nachricht -----
Von: Paulo Sérgio Medeiros
Gesendet: 06.09.10 22:01 Uhr
An: [email protected]
Betreff: [jbehave-user] Parametrizing stories
Hi,
I'm testing an workflow application where many stories are dependent on
others.
Thus, there are many cases where two stories depend on the same story but
with different parameters.
One very simple example is the stories that depend on the login story.
The
following case illustrate the scenario:
request_registration() -> authentication(user1,pass1)
request_approval() -> authentication(manager1,pass2)
'->' represents the dependency relationship between stories and the
parenthesis represent the parameters passed from one story to another.
So, in the example above, the story request_registration depends on the
authentication story passing two parameters (a user and his password).
Note
that the request_approval story also depends on the authentication story,
but with different parameters.
Does any one have this same need? Does jbehave already implements
something
that can be used to get this behavior?
Thanks!
Paulo Sérgio.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
