Thanks for the feedback. We finally all voted for JBehave - there were no alternative votes.
Now lets see how this is going to 'behave' in practice :-) Cheers - Philipp On 06.05.2011, at 13:30, Philipp Bärfuss wrote: > Hi, > > You might have noticed, by skimming the sent protocol, that we had a workshop > on about how to write better tests. Now that the topic is risen I think it > makes sense to do the next step and decide for a framework to 'standardize' > our tests by following BDD patters. I think JDave or JBehave could be a nice > match. They are both plain Java frameworks. > > After a first glance: > > JDave > - plain Java, no text files needed > - close to what we do today just more structured > --> http://jdave.org/documentation.html > > JBehave > - easy to read, more to write > - we could potentially use our property style to define content structures > --> http://jbehave.org/reference/latest/ > > EasyB > An other alternative would be to use EasyB (groovy based) but I am not sure > if this makes things much easier. In any case I have to admit that this tests > are very readable > --> http://www.easyb.org > > I don't plan to make a big evaluation. We are simply going to vote for one. > Once we have written the next set of tests we would evaluate the choice. Any > comments suggestions are welcome. > > - philipp > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
