Haha - brilliant! I was just putting something together myself based on
the
original thread but it looks like Pat has a) beaten me to it and b) made
it
look really elegant.
Nice work. I love it when a community discussion turns into something as
cool as this. And so quickly too
Haha - brilliant! I was just putting something together myself based on the
original thread but it looks like Pat has a) beaten me to it and b) made it
look really elegant.
Just so you know, David did all the work. There was one little piece
missing, but he made it so easy that a monkey could do it. I just
happened to be that monkey
Nice work. I love it when a community discussion turns into something as
cool as this. And so quickly too
I’m having a lot of trouble understanding why stories are nice for me
as a programmer? It seems targeted towards people who don’t want to
write code. Generally speaking, I don’t see the need for that on the
projects I’m working on.
Is it possible for this to be a separate library from RSpec so that
RSpec core doesn’t become bloated?
I’m having a lot of trouble understanding why stories are nice for me
as a programmer? It seems targeted towards people who don’t want to
write code. Generally speaking, I don’t see the need for that on the
projects I’m working on.
I see stories as integral / integration tool between your examples
(controller and models) and the final user.
Also, the whole job of the story is… tell a story. I find this a
better interface than:
“Contact Page should … should not…” and so on…
Is it possible for this to be a separate library from RSpec so that
RSpec core doesn’t become bloated?
AFAIK, spec and stories run in different paths. you can just ignore
the stories part and keep using the spec one.
–
Luis L.
Multimedia systems
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi
I’m having a lot of trouble understanding why stories are nice for me
as a programmer? It seems targeted towards people who don’t want to
write code. Generally speaking, I don’t see the need for that on the
projects I’m working on.
If you have customers then stories are a great communication tool
They provide end-to-end integration tests
They help you think carefully about the feature set and value of
your application.
Stories enable better refactoring. Using mocks makes your object
specs more brittle, so changes to your code often requires changes to
the specs. Because stories work at a very high level, specifying
observable behavior of the system, you can change the underlying code
without breaking behavior.
Is it possible for this to be a separate library from RSpec so that
RSpec core doesn’t become bloated?
User stories are an integral part of BDD and as such are a part of
RSpec core. Splitting them up would be a gigantic step backwards
philosophically.
Stories enable better refactoring. Using mocks makes your object
specs more brittle, so changes to your code often requires changes to
the specs. Because stories work at a very high level, specifying
observable behavior of the system, you can change the underlying code
without breaking behavior.
In a similar way, because they are so high-level, you drive much more
development per line of story than you do per line of spec. In fact,
you usually generate far more lines of specs than code, where a story
can exercise far more lines of code than it takes to write. For
people like me, who need to see progress to make progress, this is a
big big win.