Skip to content
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

Allure.NUnit: Report exceptions from OneTimeSetUp methods of class fixtures #479

Open
1 of 3 tasks
delatrie opened this issue Apr 2, 2024 · 3 comments
Open
1 of 3 tasks

Comments

@delatrie
Copy link
Contributor

delatrie commented Apr 2, 2024

I'm submitting a ...

  • bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

If a [OneTimeSetUp] method fails, all test results of the class fixture aren't included in the report. The error, therefore, remains unreported.

What is the expected behavior?

If possible, skipped test results should be created. That might be tricky as, at first glance, NUnit doesn't provide the list of scheduled tests (it provides the list of all tests in the class instead; the user might have selected only a subset of them).

An alternative approach would be reporting the error in a surrogate test result. We already do something similar in Allure SpecFlow and Allure Reqnroll.

What is the motivation / use case for changing the behavior?

Include the information about the error that occurred during the run. That information might be important to the user.

@DenisKorbovskyTds
Copy link

Thanks @delatrie for that Feature Request and answer in #286 , is there any ETA on such improvement?

@delatrie
Copy link
Contributor Author

delatrie commented Apr 2, 2024

Unfortunately, can't tell for sure now. Will provide you with more details as soon as I have any.

@gamerka
Copy link

gamerka commented Nov 8, 2024

For myself I made a hack adding this to my common OneTimeTearDown:

    var allure = AllureLifecycle.Instance;
    var testContext = TestContext.CurrentContext;
    var stackTrace = testContext.Result.StackTrace;
    var pattern = @"at (?<className>[\w\.]+)\.(?<methodName>[\w`$]+)";
    var preparedStackTrace = stackTrace?.Replace("_", "");

    if (preparedStackTrace == null ||
        (!preparedStackTrace.Contains("OneTimeSetUp", StringComparison.InvariantCultureIgnoreCase) &&
         !preparedStackTrace.Contains("InitFramework", StringComparison.InvariantCultureIgnoreCase))) return;

    var methodName = Regex.Match(stackTrace!, pattern).Groups["methodName"].Value;

    allure.StartTestCase(new TestResult
    {
        name = testContext.Test.DisplayName,
        fullName = testContext.Test.FullName,
        status = Status.broken,
        start = DateTimeOffset.UtcNow.ToUnixTimeMilliseconds(),
        statusDetails = new StatusDetails
        {
            message = $"{testContext.Result.Outcome.Status} in {methodName}.\n" +
                      $"{testContext.Result.Message}",
            trace = testContext.Result.StackTrace
        }
    });

    allure.StopTestCase();
    allure.WriteTestCase();

    allure.StopTestContainer();
    allure.WriteTestContainer();

It works for my cases and in any way it just makes Allure reports not 100% green and that's the main thing.

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

No branches or pull requests

3 participants