How well does easyb scale? Are there examples of non-trivial stories?

[Brian]

I've only recently gotten exposed to easyb and am interested but also
wondering how it scales beyond trivial poker or stack-push examples.

How does the system hold up in terms of ease and readability when the
behavior you're testing would normally be 50-100 lines in a junit
test?

Thanks.

Brian

[Andy]

Brian - it sounds like a 100 line JUnit test would be doing a lot of
work -- I would think that using something like easyb would at least
clarify things more nicely (provided you describe things well in the
story format) note too, that by using Groovy you might be able to cut
down on the amount of code. As far as moving beyond trivial examples,
there are people using easyb in real life scenarios successfully
without major issues as far as I'm aware of. I'm presently using it at
a large client without any issues -- we also use JUnit where
appropriate as easyb isn't a replacement for JUnit but a nice
enhancement.

easyb uses easyb to validate itself -- there are close to 200
behaviors which you could check out and run to see how things read,
etc?

[Brian Tarbox]

Thank you.  I really like th eidea of easyb, I just wanted some assurance that it could go beyond the examples. 

 

In my current project we've found far too many bugs in code that has > 90% code coverage.  We're testing the individual methods but not testing the actual User Stories.  I've been trying to change our test writing to have a story focus.  I'll trying using easyb but I think it will have to be descrete...my company is still absorbing the concept of spring and groovy...I don't think they'll react well to another change until I can prove it to them.

 

Thanks.

--

You received this message because you are subscribed to the Google Groups "Easyb Users" group.
To post to this group, send email to easyb...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/easyb-users?hl=.

--
Wabi Sabi Software blog: briantarbox.blogspot.com

[Brian Tarbox]

I've started using easyb and I can start to appreciate it's power.  My stories do not seem to end however.   I have one scenario, I see "1 behavior ran with no failures" but the easyb program does not finish.  If I control-c it I get a valid -txtstory file.

 

Any suggestions?  The code I'm running is basically lifted from a working junit groovy file.

 

Thanks.

Brian

--

You received this message because you are subscribed to the Google Groups "Easyb Users" group.
To post to this group, send email to easyb...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/easyb-users?hl=.

[Brian Tarbox]

Another question if I might.  I'm having some trouble understanding the verification that happens in an ensure clause.

 

I've put

  then "verify throwing exception", {

      "throw new Exception("foo")

  }

 

in a story and when I run it I get:

"Scenarios run: 1, Failures: 0, Pending:0"    but then when I cat my -txtstory file I see

 

"then verify throwing exception [FAILURE: foo]"

 

I feel like I'm missing a bit of basics here about verification.  I'd like to put junit asserts into my ensure clauses but they also don't seem to trigger failures.

 

I've tried reading the docs but no luck so far.  Any guidence would be appreciated.  Thanks.

 

Brian

[Andrew Glover]

looks like you have a " before the throw? That could be an issue.

Sincerely,

Andrew Glover
703.577.0830 (cell)

[Andrew Glover]

that's strange -- what is your story doing? I've not seen easyb hang unless the story itself does something strange. How are you invoking the story?

On Thu, Nov 19, 2009 at 2:42 PM, Brian Tarbox <brian...@gmail.com> wrote:

--