"Andy Zimmerman" <[EMAIL PROTECTED]> wrote on 10/04/2007 14:05:03:
> Liz, > > Thanks for the thoughtful reply. I *think* I'm starting to "get" it. > I'll let you know how my efforts at adopting jBehave go. > > The primary difference for me is going to be that I don't have a Java > GUI; I'm working strictly in the web app space, so I need to adapt > things slightly. Any recommendations / experiences that anyone has > working with jBehave in that environment would be greatly appreciated. > > Thanks, > Andy Hi Andy, Good news: We have exciting plans to integrate a really cool web harness with JBehave (see code.google.com/p/webdriver !) Bad news: We haven't started yet. So, you have a gui (web page) which gives value to the Story, and whose behaviour is difficult to describe in code. You can either: - manually verify the behaviour of the web page, and start the executable Stories at the next layer which gives value to it (eg: the container) - or be brave and hook a suitable web app into JBehave. I have done the first on a commercial web app with a fair degree of success (some third-party app configuration and possible proxying required). Whatever you decide (and especially if you go with the second!) please let us know how it goes! Cheers, Liz. -- Elizabeth Keogh [EMAIL PROTECTED] http://sirenian.livejournal.com http://jbehave.org
