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

There is no way to debug a method marked as AllureStep #521

Closed
1 task done
kiragengis opened this issue May 29, 2024 · 1 comment
Closed
1 task done

There is no way to debug a method marked as AllureStep #521

kiragengis opened this issue May 29, 2024 · 1 comment
Labels
type:bug Something isn't working

Comments

@kiragengis
Copy link

Describe the Bug

When debugging code in C# with Visual Studio 2022 version 17.9.5 in Windows, any method marked with [AllureStep] does not allow inspecting (Quick Watch) the local variables. You can see the value of the parameters but not the local variables.

Steps to Reproduce

Debug this code with Visual Studio. Put a breakpoint at the end of the methods MethodWithStep and MethodWithoutStep.

[Test]
public void Test1()
{
    MethodWithStep();
    MethodWithoutStep();
}

[AllureStep]
public void MethodWithStep() 
{
    int notVisibleVariable = 7;
}

public void MethodWithoutStep()
{
    int visibleVariable = 7;
}

Expected Behaviour

During debugging, the person should be able to see the value of the variable notVisibleVariable

Screenshots or Additional Context

This is the output from the method with a Step:
image

This is the output from a method without a Step
image

What Language are you using?

C#

What Framework/Allure Integration you are using?

allure-nunit

What version of Allure Integration you are using?

2.11

What version of Allure Report you are using?

2.11

Code of Conduct

  • I agree to follow this project's Code of Conduct
@kiragengis kiragengis added the type:bug Something isn't working label May 29, 2024
@baev baev transferred this issue from allure-framework/allure2 Jun 10, 2024
@kiragengis
Copy link
Author

This problem is fixed in AspectInjector version 2.8.2. I am closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant