Releases: addupsolutions/AddUp.FakeRabbitMQ
Releases · addupsolutions/AddUp.FakeRabbitMQ
v2.8.0
- Fixed Issue #180: Now non-AutoAck scenarios work better (not sure though if they are completely equivalent to what a real RabbitMQ instance would do).
Note that this version might be technically breaking as some
public
members are now eitherinternal
or implemented rather differently.
Anyway those are implementation details and should not be used from client code. I intend to internalize more implementation details in the future so as to not leak abstractions.
Also note that this is far from being bulletproof: The unit tests associated with issue #180 pass, but there are still many scenarios that do not work the same as with a real RabbitMQ server (for example, do not try to requeue a
nacked
message, it won't work).
v2.7.0
v2.6.0
v2.5.0
Two contributions by @patrikwlund:
- Better compliance: No more unique singleton-based connection. See PR #122 for details.
- New feature: by passing a boolean to the constructor of
AddUp.RabbitMQ.Fakes.RabbitServer
, one can opt into using blocking delivery (the default remains non-blocking). This helps simplifying unit tests in scenarios where one is not interested in simulating a real RabbitMQ behavior (avoids asynchronous waiting for messages delivery). See PR #123 for details.
v2.4.0
v2.3.0
v2.2.0
v2.1.0
v2.0.0
Based on RabbitMQ.Client version 6.2.4
v1.5.1
Updated dependencies (obviously except for RabbitMQ.Client that is still version 5.2.0)