Print the scenario's log entries when an acceptance test fails - #5876
Merged
Conversation
The test endpoints log only into ScenarioContext.Logs, and nothing printed those, so a failure could not be traced past ServiceControl's own output. The Windows-PostgreSql failure that hung in SendLocal for a minute is the example: the receiver endpoint left no trace at all. TearDown now prints the entries the way NServiceBus core's acceptance tests do.
irinascurtu
approved these changes
Sep 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The test endpoints log only into
ScenarioContext.Logs, and nothing printed those, so a failing acceptance test could not be traced past ServiceControl's own output. A recent Windows-PostgreSql failure spent a minute insideSendLocaland the receiver endpoint left no trace at all.NServiceBusAcceptanceTest.TearDownnow prints the entries on failure, timestamped and labelled by endpoint, the way NServiceBus core's acceptance tests do. ServiceControl's host logs into the same collection on top of its live output, so its lines appear twice for a failed test.