Skip to content

Standard test output is not logged to allure for failed tests, but lo… #32

Open
wants to merge 15 commits into
base: master
Choose a base branch
from

Conversation

sphinxy
Copy link
Contributor

@sphinxy sphinxy commented Feb 1, 2023

…gged for success test.

Fixes #31

@sphinxy
Copy link
Contributor Author

sphinxy commented Feb 1, 2023

tested, now we have test output in *result.json for failing tests too.

 "name": "Test output is logged for failed test",
  "status": "failed",
  "statusDetails": {
    "known": false,
    "muted": false,
    "flaky": false,
    "message": "This failed assert is logged too along with previous output\r\nExpected: False\r\nActual:   True\nThis output of failed test should be visible in IDE and in logged allure-result/*result.json\r\n",
    "trace": "   at Xunit.Assert.False(Nullable`1 condition, String userMessage) in C:\\Dev\\xunit\\xunit\\src\\xunit.assert\\Asserts\\BooleanAsserts.cs:line 52\r\n   at Xunit.Assert.False(Boolean condition, String userMessage) in C:\\Dev\\xunit\\xunit\\src\\xunit.assert\\Asserts\\BooleanAsserts.cs:line 40\r\n   at Allure.XUnit.Examples.ExampleUnitTests.TestStandardOutputSavedToAllureForFailedTest() in C:\\_work\\Allure.XUnit\\src\\Allure.XUnit.Examples\\ExampleUnitTests.cs:line 86"
  },

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Standard test output is not logged to allure for failed tests, but logged for success test
1 participant