Excellent!!! Just what I'd needed and never found - dunno why. I kind of improvised part of this (I used remote and local versions of a model elsewhere), but this work work just fine for me, and I can use it to simplify the other usages as well. I can then fake everything I need through configuration.
All the best Stuart On 2010-01-17, at 8:56 PM, Tomas Doran wrote: > > On 17 Jan 2010, at 22:07, Stuart Watt wrote >> >> What I wanted to be able to do was mock out the remote job queue web >> service, so at least I could check out that the front end render stuff >> without to put an entire web server temporarily in place. Basically, I'd >> hoped to replace the model that implements the web service and check that >> the right stuff goes in and out. > > Right - and _THIS_ is why you implement your model classes outside of > Catalyst, and bind them in. > > If you are using Catalyst::Model::Adaptor to bind an external class, then > changing the implementation of the model class to a mock class in your test > suite is a simple case of providing some config to change the name of the > class which is adapted... > > Cheers > t0m > > > _______________________________________________ > List: [email protected] > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: http://www.mail-archive.com/[email protected]/ > Dev site: http://dev.catalyst.perl.org/ > > -- > This message was scanned by ESVA and is believed to be clean. > Click here to report this message as > spam.http://antispam.infobal.com/cgi-bin/learn-msg.cgi?id=358052807F.E175C > _______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
