Hi Christopher,
the builder pattern is a very useful pattern, that I've used effectively
precisely in BDD projects for the scope you suggest. IMO it's more
effective and flexible than the object mother pattern, which is adequate
for very simple object creation but very rapidly shows its limitations
(as Nat rightly suggests).
To scratch an itch I've been having for a few days, I've also added a
builder for scenario reporters.
http://jira.codehaus.org/browse/JBEHAVE-228
Cheers
Christopher Gardner wrote:
With respect to using JBehave for integrated acceptance tests, I've
been thinking about the approach Nat Pryce takes with test builders in
his book Growing Object-Oriented Software, Guided by Tests and here:
http://nat.truemesh.com/archives/000714.html
The Given methods can use the data in the Example Tables rows to feed
the test builders and the JPA for persisting the products of the
builders.
On Fri, Dec 25, 2009 at 7:56 AM, Christopher Gardner
<[email protected]> wrote:
I'm curious how JBehave users typically do setup. Do you use a tool
such as DbUnit, JPA/Hibernate, or some combination thereof (a la
unitutils)? It seems that for Table Examples and Table Parameters
(http://jbehave.org/reference/latest/table-parameters.html), it would
be appropriate to use JPA/Hibernate.
---------------------------------------------------------------------
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
