Am 12.03.2010 um 02:12 schrieb Julian Leviston: > This is great, but code should be easy enough to understand that anyone can > read it... like, say, an even "easier" and better version of Cucumber. Do > that kind of binding, and I see there being no difference between writing > down the goals in these two ways. > > http://cukes.info/ > > What disappoints me about Cucumber is that, along with most things I see > these days, it doesn't really address "scale". Some descriptions need to be > very BIG PICTURE, and others need to be more about intimate detail. It'd be > good to have some kind of system which respected this.
I'd love to see an extension of the "Given When Then" approach of Cucumber towards "Given When Then Return" approach. Then suddenly rules could be composed by plugging the "Return" values into the "Given". More on example composition: "Composing Tests from Examples" (Journal of Object Technology) http://www.jot.fm/issues/issue_2007_10/paper4.pdf JExample http://scg.unibe.ch/research/jexample PHPUnit http://sebastian-bergmann.de/archives/848-Fixture-Reuse-in-PHPUnit-3.4.html Cheers Markus _______________________________________________ fonc mailing list [email protected] http://vpri.org/mailman/listinfo/fonc
