Last night someone brought to my attention that the current versions of PipelineTesting always
return null from the IPipelineContext.GetEventStream() method.
This is expected to return an EventStream object
so that pipeline components can write to BAM, but I never had bothered looking it
up before.
I’ve now fixed this so that the property returns an EventStream-derived class that
simply swallows all calls to it silently, to avoid tying the library to having any
specific BAM infrastructure in place, and this will be included in the next version
of the library.
Is this good enough? Is there anyone who would prefer to have a way to override this
behavior so that a real, connected BAM EventStream object is provided? Does someone
need a way to check as part of the test assertions that specific events were indeed
written to the EventStream? If so, I may look into a way to support this nicely, otherwise,
I’ll leave it as is for now.
PipelineTesting, BizTalkServer