Module testing 

In-process test broker, behind the testing feature.

The broker follows the same ladder as the real one (synchronous new, consuming connect, consuming shutdown) over an in-memory router, so application handlers wired against RabbitMQ descriptors can be exercised without a server: messages fan out synchronously to subscribers matched by exact queue name. Public surface:

• LapinTestBroker / ConnectedLapinTestBroker - the ladder; the connected form implements TestableBroker, so it drives both the TestApp harness and the framework’s conformance suite;
• LapinTestPublish / LapinTestPublisher - the publish pair, carrying both transaction kinds: the handle-level borrowed one and the owned LapinTestTransaction;
• LapinTestSubscriber / LapinTestMessage - the Subscriber and IncomingMessage impls, settling like the real transport.

Scope: queue-name routing, settlement, headers, and buffered transactions. Exchange types, bindings, dead-lettering, prefetch, and request/reply are transport behavior; exercise them against a real server (see the crate’s integration tests and AMQP_TEST_URL).

Structs

ConnectedLapinTestBroker

The connected form of LapinTestBroker.

LapinTestBroker

In-process broker for application tests: same descriptors, no RabbitMQ server.

LapinTestMessage

One in-process delivery.

LapinTestPublish

The in-process publish policy, mirroring LapinPublish on the real broker.

LapinTestPublisher

The live publisher into the in-process router.

LapinTestSubscriber

In-process subscriber on one queue name.

LapinTestTransaction

An owned in-process transaction, opened by transaction on a LapinTestPublisher.