Allure.NUnit 2.9.2-preview.1 logs start and result of each step to console

[andrematosfundao]

I'm submitting a ...

• bug report

What is the current behavior?

This library is outputting to console each start of a step, the step name and the result of each step.

seems to me some leftover debug logging.
this issue create lots of console logs for tests with many steps and make it difficult to find other relevant information that may have been ouputed to the console.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

any test with a step can generate this on the version Allure.NUnit 2.9.2-preview.1.

 [AllureStep("isLogedinValidationStep")]
    private void isLoggedin()
    {
    }
    [AllureStep("LoginSubStep")]
    private void sublogin()
    {
    }
    [AllureStep("LoginStep")]
    private void login()
    {
        sublogin();
    }

    [Test]
    [AllureName("test1")]
    public void Test1()
    {
        login();
        isLoggedin();
    }

What is the expected behavior?

I believe that the allure library should output nothing to the console by default.

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

cleaner console output

Please tell us about your environment:

• Test framework: Nunit@3.13.3
• Allure adaptor: Allure.NUnit@2.9.2-preview.1

Other information

seems to me that the console logs are generated here:

allure-csharp/Allure.XUnit/Steps.cs

Line 82 in 7177073

Log($"Started Step: {name}");

allure-csharp/Allure.XUnit/Steps.cs

Line 104 in 7177073

Log("Passed");

[undron]

Hi, I've made PR to remove this calls with ability to add own logger to steps.
As for me, it is useful to have steps in text logs

[neparij]

@undron Andrey, thanks for PR!

[andrematosfundao]

@undron Nice work.

[neparij]

Hello everyone!
You can try it out in 2.9.3-preview.1 release

[andrematosfundao]

can confirm it works fine now on 2.10