Re: Using Test::MockObject For Good And Evil

You could certainly do this, but you're probably better off building your own interface-compatible modules instead.

The key is in putting an AUTOLOAD in your own object and having it report the unimplemented methods. Then go through and implement them.

Comment on Re: Using Test::MockObject For Good And Evil

Replies are listed 'Best First'.
Re^2: Using Test::MockObject For Good And Evil by jk2addict (Chaplain) on Mar 16, 2005 at 23:06 UTC
That's where I get a little fuzzy. I'd like to use as much of the CPANTS modules as possible. I think I can get away with using ::CPAN, ::Files, ::FindModules, ::Pod, ::Prereq, ::Unpack, and ::Uses without to much hackery jigery pokery. I could reimpliment my own versions of these test, but I really don't want too, especially if they change over time. The base module on the other hand is a different story.	[reply]

Replies are listed 'Best First'.

Re^2: Using Test::MockObject For Good And Evil
by jk2addict (Chaplain) on Mar 16, 2005 at 23:06 UTC

That's where I get a little fuzzy. I'd like to use as much of the CPANTS modules as possible. I think I can get away with using ::CPAN, ::Files, ::FindModules, ::Pod, ::Prereq, ::Unpack, and ::Uses without to much hackery jigery pokery. I could reimpliment my own versions of these test, but I really don't want too, especially if they change over time.

The base module on the other hand is a different story.

[reply]