You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I dump out debugging info via XUnitOutput.WriteLine, and then I find a condition that requires the Skip feature, but the XUnit test 'Output' has lost debugging info, and only Skip comment shows.
It would be better if both the XUnitOutput.WriteLine as well as the Skip comment would show in the test 'Output' (and also the Skip comment be visible in the XUnit side window like say "Message: The collection was expected to contain a single element, but it was empty." rather than having to view 'Output').
The text was updated successfully, but these errors were encountered:
I dump out debugging info via XUnitOutput.WriteLine, and then I find a condition that requires the Skip feature, but the XUnit test 'Output' has lost debugging info, and only Skip comment shows.
It would be better if both the XUnitOutput.WriteLine as well as the Skip comment would show in the test 'Output' (and also the Skip comment be visible in the XUnit side window like say "Message: The collection was expected to contain a single element, but it was empty." rather than having to view 'Output').
The text was updated successfully, but these errors were encountered: