Re: changing object's methods at runtime

If you need to fake Apache request object for test purposes you may find it is much easier to use mock objects (i.e. Test::MockObject) instead of Apache::FakeRequest as you have more control over fake request object. See Automated software testing: emulation of interfaces using Test::MockObject for example.

--
Ilya Martynov, ilya@iponweb.net
CTO IPonWEB (UK) Ltd
Quality Perl Programming and Unix Support UK managed @ offshore prices - http://www.iponweb.net
Personal website - http://martynov.org

Comment on Re: changing object's methods at runtime

Replies are listed 'Best First'.
Testing mod_perl handlers [was Re: changing object's methods at runtime] by ViceRaid (Chaplain) on May 21, 2003 at 14:03 UTC
Thanks Ilya Actually, I started off with Test::MockObject to fake the request, but there was a lot of methods I needed to mock and that's a bit laborious. The other reason is that Apache::Request conveniently fills out all the Apache::Constants, eg, `Apache::Contants::FORBIDDEN` which otherwise need to be set manually as they're unavailable when running outside mod_perl. But having tried it both ways now ;), there's really not much in it.	[reply]

Replies are listed 'Best First'.

Testing mod_perl handlers [was Re: changing object's methods at runtime]
by ViceRaid (Chaplain) on May 21, 2003 at 14:03 UTC

Thanks Ilya

Actually, I started off with Test::MockObject to fake the request, but there was a lot of methods I needed to mock and that's a bit laborious. The other reason is that Apache::Request conveniently fills out all the Apache::Constants, eg, Apache::Contants::FORBIDDEN which otherwise need to be set manually as they're unavailable when running outside mod_perl.

But having tried it both ways now ;), there's really not much in it.

[reply]