-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NUnit: IndexOutOfRangeException if AllureAfter is applied on a method with paramters #419
Closed
1 of 3 tasks
Labels
Comments
delatrie
added a commit
that referenced
this issue
Mar 26, 2024
- missing container if [AllureAfter] is applied to some, but not all OneTimeTearDown methods of a class - Fix IndexOutOfRangeException if [AllureAfter] is applied to a method with arguments
delatrie
added a commit
that referenced
this issue
Mar 26, 2024
- missing container if [AllureAfter] is applied to some, but not all OneTimeTearDown methods of a class - Fix IndexOutOfRangeException if [AllureAfter] is applied to a method with arguments
delatrie
added a commit
that referenced
this issue
Mar 27, 2024
- missing container if [AllureAfter] is applied to some, but not all OneTimeTearDown methods of a class - Fix IndexOutOfRangeException if [AllureAfter] is applied to a method with arguments
delatrie
added a commit
that referenced
this issue
Mar 27, 2024
- missing container if [AllureAfter] is applied to some, but not all OneTimeTearDown methods of a class - Fix IndexOutOfRangeException if [AllureAfter] is applied to a method with arguments
delatrie
added a commit
that referenced
this issue
Mar 27, 2024
- missing container if [AllureAfter] is applied to some, but not all OneTimeTearDown methods of a class - Fix IndexOutOfRangeException if [AllureAfter] is applied to a method with arguments
delatrie
added a commit
that referenced
this issue
Mar 28, 2024
- missing container if [AllureAfter] is applied to some, but not all OneTimeTearDown methods of a class - Fix IndexOutOfRangeException if [AllureAfter] is applied to a method with arguments
delatrie
added a commit
that referenced
this issue
Mar 28, 2024
- missing container if [AllureAfter] is applied to some, but not all OneTimeTearDown methods of a class - Fix IndexOutOfRangeException if [AllureAfter] is applied to a method with arguments
delatrie
added a commit
that referenced
this issue
Mar 28, 2024
- missing container if [AllureAfter] is applied to some, but not all OneTimeTearDown methods of a class - Fix IndexOutOfRangeException if [AllureAfter] is applied to a method with arguments
delatrie
added a commit
that referenced
this issue
Mar 28, 2024
* Improve Allure NUnit status reporting - New algorithm to distinguish between failed/broken tests. Now, a test is failed if NUnit shows at least one failed assertion and no assertion errors. The 'brokenTestData' config property is removed. - Remove empty status details for passed tests (#363) * Remove empty console log attachments from tests (#363) Additional changes: - Remove redundant config from Allure.NUnit project - Fix conflicting IgnoreTestWithTestCaseData test names in Allure.NUnit.Examples * Fix NUnit OneTimeTearDown reporting (#419) - missing container if [AllureAfter] is applied to some, but not all OneTimeTearDown methods of a class - Fix IndexOutOfRangeException if [AllureAfter] is applied to a method with arguments * Use the common skip reason for test plans * Preclude ignored tests not in a test plan from report * Remove ignored test containers Every ignored test container contains no fixtures. * Fix labeler entry for Allure NUnit examples * Change Allure NUnit namespace to Allure.NUnit Backward compatibility is implemented via OldNamespaceCompatibility * Remove deprecated API from Allure.NUnit: - AllureNUnitHelper: - WrapInStep - SaveOneTimeResultToContext - AddOneTimeSetupResult - StepsHelper * Hide internal API
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm submitting a ...
What is the current behavior?
If a method with AllureAfter and at least one parameter is called, IndexOutOfRangeException is thrown.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
The following code throws an unexpected IndexOutOfRangeException:
What is the expected behavior?
No exception is thrown, the fixture is added to the report.
What is the motivation / use case for changing the behavior?
To support custom tear down methods.
Please tell us about your environment:
Other information
This is due to invalid call at
allure-csharp/Allure.NUnit/Internals/StopContainerAspect.cs
Line 28 in 7fc8d09
The text was updated successfully, but these errors were encountered: