Saga scenario testing framework can't handle ReplyToOriginator

[DavidBoike]

Symptoms

A saga test using the TestableSaga API fails with the following Exception:

Entity.Originator cannot be null. Perhaps the sender is a SendOnly endpoint.

Another symptom is a NullReferenceException when trying to work with the Data.Originator property of the saga data.

Who's affected

Saga tests using the TestableSaga API that use the Data.Originator property or the ReplyToOriginator method in a saga under test.

Root cause

ReplyToOriginator is an oversight in the saga scenario testing framework. When the first message arrives for a saga, the TestableSaga class does not emulate the originator behavior, so the Originator property on the saga entity is left null.

Backported to

• 7.4.2