Trying out Behave#

re: Trying out Behave#

Ankit Dass — Thu, 30 Aug 2007 15:46:02 GMT

Just had a look at your bheave# example and read a bit more about it. I agree with one of your point that if you want to specify Exceptions as part of your story, this forces you to move away from [ExpectedException]. Which is a Good Thing anyway.

It is quite verbose though

I think i am going to try a real world example and see how it goes or to put it more appropriately to see if it grows on me and how comfortable i feel.

re: Trying out Behave#

casper — Thu, 30 Aug 2007 15:49:54 GMT

I agree with Brad and Jim that we should be moving away from [ExpectedException] regardless of what framework we're working in :)

The verbose-ness (I think) is one of the qualities that could make it attractive to product owners or PMs. The code is really to express acceptance tests rather than developer-focused 'unit' tests.

Please write back whenever you get a chance to try this in the real world .. I would love to see more examples :)

re: Trying out Behave#

TSHAK — Thu, 30 Aug 2007 17:52:37 GMT

I wonder, and I'm allowed to be wrong on this, if it wouldn't be more effective to A) improve our programming languages (and usage of) for readability and B) require PM's to learn these languages. "But a PM would never learn...." it seems a lot easier (and cheaper) than forcing developers to learn *and* maintain this overly verbose artifact.

re: Trying out Behave#

casper — Thu, 30 Aug 2007 17:59:05 GMT

A) Yes

B) Yes

I guess in the meantime, it's interesting to see what we can accomplish with the tools we have :)

Re the 'developers learning/maintaining stuff' .. you can bet that there is already work going on to do the translation from spoken language wiki documents (à la Fitnesse) to what I'm demonstrating here and more.

re: Deep Dive into TDD Revisited

Brian Button - One Agile Coder — Thu, 30 Aug 2007 18:37:39 GMT

Esplorando il Behaviour Driven Development

makka — Sun, 02 Sep 2007 17:21:13 GMT

Esplorando il Behaviour Driven Development

re: Trying out Behave#

Joe Ocampo — Tue, 04 Sep 2007 06:18:48 GMT

@casper

Thanks for trying out the framework. The focus of NBehave(aka behave#) from the story runner perspective is to find a new way for product owners and developers to interact on a given problem domain.

Our goal is that the product owners would actually be interacting with the developers during the planning sessions of a release within the IDE. I have done this several times already and it has proven very successful.

I mentioned it here:

http://www.lostechies.com/blogs/joe_ocampo/archive/2007/07/15/more-bdd-xbehave-madness.aspx

I would appreciate your feedback on real world examples. Jimmy, Morgan and myself are always looking at ways to improve the usability of the DSL (fluent interface).

Thanks again

re: Trying out Behave#

casper — Tue, 04 Sep 2007 06:32:59 GMT

Hi Joe,

Thanks for the comments :) I'll definitely let you know how it works in the real world. It would also be really great to get some different (and more complex) examples than the Account one.

re: Trying out Behave#

Joe Ocampo — Tue, 04 Sep 2007 18:14:42 GMT

I couldn't agree with you more! I am getting tired of using the accounting example. I was thinking of something like a role playing game but that doesn't really apply to a majority of the vertical markets out there. May go with the traditional Video Store example.

Nelson Montalvo has a 5 part series on using Behave#; he is using it to build the application he is working on.

http://codemonkey.nmonta.com/2007/08/14/behave-part-5/