Justin Rudd [mailto:[EMAIL PROTECTED]] wrote:
> I'm very familiar with Mock Objects
> (http://abstractadonet.sourceforge.net/mock.html).
Cool stuff... and this is much simpler with the System.Data namespace since
they actually did factor it all out into interfaces.
> My
> question was really a
I ran into exactly this scenario in a Java project. I did what Drew
suggests here - I created my own abstraction on top of the queue.
(Actually when I started writing it was still up in the air as to exactly
which package we were going to use for message queueing - we had to connect
a Java syste
Hi Drew,
> Lots of people do this, it's a well-known testing
> pattern referred to as Mock Objects[1].
I'm very familiar with Mock Objects (http://abstractadonet.sourceforge.net/mock.html).
My question was really a request for comments. I was wondering HOW people are
approaching the problem.
Justin Rudd [mailto:[EMAIL PROTECTED]] wrote:
> I was wondering, how many people do this? What are some
> other ways that you are accomplishing the same thing?
Lots of people do this, it's a well-known testing pattern referred to as
Mock Objects[1].
However, you run into a problem using Mock O
Let's say that I have the following (useless) method...
public void GetMessage() {
Message m = _messageQueue.Receive();
}
Now I'm tied to MSMQ (which is not the problem), but it makes it hard to test because
I've got to preload a queue with messages before I can test.
What if I did this..
