On Jan 17, 2008 11:33 AM, Giles Bowkett <gilesb at gmail.com> wrote:
> > Giles - I think you'll find more people with more experience in this
> > area on the testdrivendevelopment at yahoogroups.com list. That said, and
> > only having glanced at your mail, here's a thought or two:
> >
> > The TDD line on this, as I understand it, is that you should write
> > your main application code exactly as you want to write it, imagining
> > that you had the perfect API to talk to and stubbing that API in your
> > tests. Then, when hooking up to the real services, you write thin
> > adapters that simply convert messages to the right format. I *think*
> > that's what you said you are doing.
>> Yes. Sorry about the Great American Novel - that is pretty much what I'm doing.
Then that's sane :)
It lets you keep changes to your internal app separate from changes to
the service - even allows you to easily swap in new services - and
lets you "talk in your language" within the app rather than being
subject to an API that may or may not make sense to you most of the
time.
>> --
>> Giles Bowkett
>> Podcast: http://hollywoodgrit.blogspot.com> Blog: http://gilesbowkett.blogspot.com> Portfolio: http://www.gilesgoatboy.org> Tumblelog: http://giles.tumblr.com> _______________________________________________
> rspec-users mailing list
>rspec-users at rubyforge.org>http://rubyforge.org/mailman/listinfo/rspec-users>