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
If we use xunit's TestOutputHelper to log something, it also appear in allure, but only for success tests. For failed tests exceptions are logged but test output is missing in allure.
So if we have some debug output like "Sample test userId = 123", test start failing and we compare test results, we don't see useful debug info in comparison.
e.g. for imaginary test GetUserNameByUserId() with some logging inside:
Success test sample output :
"Sample test userId = 123"
"Received username is Oleg"
Current failed test output: "Assert.Equal() Failure (pos 0) Expected: "Oleg" Actual: "MissingName"
If we use xunit's TestOutputHelper to log something, it also appear in allure, but only for success tests. For failed tests exceptions are logged but test output is missing in allure.
So if we have some debug output like "Sample test userId = 123", test start failing and we compare test results, we don't see useful debug info in comparison.
e.g. for imaginary test GetUserNameByUserId() with some logging inside:
Success test sample output :
Current failed test output:
"Assert.Equal() Failure (pos 0) Expected: "Oleg" Actual: "MissingName"
Fixed new failed test output:
The text was updated successfully, but these errors were encountered: