I wouldn't mind putting this as a separate project.Just take into account
that a LOT of things happen at the transport layer, such as the transaction
management part.


On Thu, Sep 3, 2009 at 7:13 PM, Jason Meckley <[email protected]>wrote:

>
> I definitely agree MSMQ needs to be tested, but should MSMQ tests be a
> part of RSB? The only reason I raise this point is because RSB does
> give us a choice between RQ and MSMQ.
>
>
> On Sep 3, 12:02 pm, Ayende Rahien <[email protected]> wrote:
> > Jason,a) we need to test the MSMQ implementation somehow.
> > b) I would probably be a good idea, yeah.
> >
> > On Thu, Sep 3, 2009 at 7:00 PM, Jason Meckley <[email protected]
> >wrote:
> >
> >
> >
> > > I attempted to compile RSB from GitHub this morning to be greeted with
> > > a large number of failing test. I quickly realized they are failing
> > > because MSMQ is required for testing. I grabbed the binaries from the
> > > build directory (rather than release) and updated my application.
> >
> > > a few hours later I thought: RSB can use MSMQ or RQ for message
> > > processing, so why would the tests require MSMQ (or RQ for that
> > > matter)? Wouldn't the tests use a mock/fake to handle the queueing?
> > > This way RSB can successfully complete a build (psake) without MSMQ or
> > > RQ. Another option: have a flag in the build stript to test with RQ or
> > > MSMQ. I would think this is much more work than using a fake queue.
> >
> > > Taking that a step farther, wouldn't it make sense to separate the
> > > MSMQ provider into a separate assembly, just like RQ? If you're using
> > > the MSMQ provider it would be installed and the tests would pass
> > > because MSMQ is part of the infrastructure.
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Rhino Tools Dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rhino-tools-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to