Allure.NUnit improvements

[delatrie]

Context

This PR improves the user experience with Allure NUnit.

Change of the namespace

The main namespace of the package now is Allure.NUnit. Users should adapt their code accordingly:

• NUnit.Allure.Core.AllureNUnitAttribute -> Allure.NUnit.AllureNUnitAttribute
• NUnit.Allure.Attachments -> Allure.NUnit.Attachments
• NUnit.Allure.Attributes.* -> Allure.NUnit.Attributes.*

The old NUnit.Allure namespace is still in place, but accessing it will trigger a deprecation warning.

Improved error statuses reporting

Fixture and step errors

From a user's perspective, nothing has changed. The decision is not made by the code in Allure.Net.Commons, but the result is the same: exceptions of types AssertionException and NUnitException make the step/fixture failed while exceptions of other types - broken.

Test errors

NUnit considers a test failed in the following cases:

• a test throws an unhandled exception (including assertion-related exceptions)
• at least one failed assertion occurred during the test (regardless of whether the exception was handled).
  NUnit doesn't give us an instance of the exception — only the list of assertion results and a final error message.

Previous implementation

An Allure test result is considered broken if the corresponding NUnit test error message contains at least one entry from the brokenTestData configuration property (typically, full names of exception types that should make tests broken). Otherwise, the test result is considered failed.

That requires users to put all possible exception types in the config. Otherwise, test defects are reported as product ones.

New implementation

An Allure test result that corresponds to a failed NUnit test is considered broken in any of the following cases:

• It doesn't have any assertion, or
• It contains an invalid assertion (of status AssertionStatus.Error) - that corresponds to an unhandled exception.

Additionally, inconclusive tests and tests with warnings are reported as broken (that stayed the same).

The brokenTestData configuration property is ignored from now on.

Api deprecation and removals

The following API is deprecated now:

• AllureExtensions:
  • WrapSetUpTearDownParams: it had no effect.
  • WrapInStep (all overloads): use AllureApi.Step instead.

The public API that had been previously deprecated was removed.

• AllureNUnitHelper:
  • WrapInStep: use [AllureStep] or AllureApi.Step instead.
  • SaveOneTimeResultToContext: hadn't meant to be public.
  • AddOneTimeSetupResult: hadn't meant to be public.
• StepsHelper: use [AllureStep], AllureApi, or ExtendedApi instead.
• AllureNUnitAttribute,s constructor with the bool wrapIntoStep parameter (had no effect).
• AllureExtensions:
  • AddScreenDiff: use AllureApi.AddScreenDiff instead.

The following API that was meant to be internal is now hidden:

• AllureNUnitHelper.GetNUnitStatus and the entire AllureNUnitHelper class.

Other changes

• Empty console logs and status details are not included in the report now (fixes Preclude empty console logs and status details from the report produced by allure-nunit #363)
• Fixed missing container if [AllureAfter] is applied to some but not all [OneTimeTearDown] methods of a test fixture.
• Fixed IndexOutOfRangeException if [AllureAfter] is applied to a method with arguments (fixes NUnit: IndexOutOfRangeException if AllureAfter is applied on a method with paramters #419).
• Allure NUnit now uses the common skip reason for tests excluded by a test plan.
• Ignored tests not in the current test plan are not reported even if [AllureDisplayIgnoredAttribute] is applied.
• allureConfig.json was removed from Allure.NUnit source code.
• Now, we don't emit empty containers for ignored tests.
• An ignored test from Allure.NUnit.Examples was renamed so as not to collide with its non-ignored counterpart.
• Labeler entry was fixed for Allure.NUnit examples project.