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 was taking a look to the AllureNUnitHelper and I was able to see that the IsBroken function is waiting elements in result.Assertions list but when you use FluentAssertions or Playwright this list is not update so the tests are always mark as broken.
The text was updated successfully, but these errors were encountered:
Hello, I have the same issue,
I am using Xunit, Allure.Net.Commons and Shouldly
When I run a test with this simple step, and generate an Allure report
the test status displayed as Broken
Also, I tried to add the Shouldly.ShouldAssertException to the allureConfig.json, the step becomes Failed but the test is still displayed as Broken
I'm submitting a ...
What is the current behavior?
The test case failed using fluentassertions or Playwright are shown as broken instead of failed
If the current behavior is a bug, please provide the steps to reproduce and, if possible, a minimal demo of the problem
Create a simple test using FluentAssertions or Playwright dotnet, when you run the tests the resutl is shown as broken
![image](https://private-user-images.githubusercontent.com/162322781/338074459-65d64dba-6041-4c8e-8c6f-8c808156ae2d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAxODkxMDksIm5iZiI6MTcyMDE4ODgwOSwicGF0aCI6Ii8xNjIzMjI3ODEvMzM4MDc0NDU5LTY1ZDY0ZGJhLTYwNDEtNGM4ZS04YzZmLThjODA4MTU2YWUyZC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzA1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcwNVQxNDEzMjlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zNTVkMDlhYWFlNmUxOTEyZGY4NWUxMzEwYTExYTgwM2NiNmVmZmY0ODQ5NjQ2YzhhOTg4ZTVkMzhkNTUwNmU5JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.MK6YtsBe4xkkR_fq9Se1rHftLKSk_ntsMtlTvbPRHCU)
What is the expected behavior?
The test should be failed if I have configured the list of exceptions (failExceptions).
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Other information
I was taking a look to the AllureNUnitHelper and I was able to see that the IsBroken function is waiting elements in result.Assertions list but when you use FluentAssertions or Playwright this list is not update so the tests are always mark as broken.
![image](https://private-user-images.githubusercontent.com/162322781/338076191-502e443e-f0e5-4aed-9447-d1a649b62f74.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAxODkxMDksIm5iZiI6MTcyMDE4ODgwOSwicGF0aCI6Ii8xNjIzMjI3ODEvMzM4MDc2MTkxLTUwMmU0NDNlLWYwZTUtNGFlZC05NDQ3LWQxYTY0OWI2MmY3NC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzA1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcwNVQxNDEzMjlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1mNTA5NmRhNWY3NzE2NWJjNzMxNmRmMDYxYWVlY2NkYzQ4YmViMWFkYmQ2ZGM4YWEzZDdjZjcwNzI5YTg3ZWM3JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.kLOF0JzBZ_tPUxSdDEH5EMS_Jb_MFe0V7Fv-8jG3uOc)
The text was updated successfully, but these errors were encountered: