allure-framework / allure-framework/allure-csharp

Edit and continue does not work due to usage of AspectInjector 2.6

Open
#304 4 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
C#
Stars
125
Forks
76
Avg merge
1d 2h
Merged PRs (30d)
18

Description

#### I'm submitting a ...
- [X] 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?

Cannot use edit and continue on debug mode when allureStepAttribute is used

see this [video of the failure](https://user-images.githubusercontent.com/33062016/203816135-96ff9d5b-7efc-4b56-b632-46f57157ab9f.gif)

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

in the code bellow put a break point on the test
run in debug mode
edit the string
continue execution
it fails

[code example](https://github.com/allure-framework/allure-csharp/files/10085601/EditAndContinueIssue.zip)

#### What is the expected behavior?

we should be able to use edit and continue since it is such a great tool for development

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

making edit and continue work as expected.

#### Please tell us about your environment:

net7.0





#### Other information

I believe to fix this it is only necessary to update to AspectInjector 2.7

as a temporary fix i copied the code for AllureStepAttribute in my project and use the latest aspectInjector and that works for me.

Contributor guide

Open the contributing guide

Research direction

Start with the attached EditAndContinueIssue.zip reproduction and the NUnit.Allure package setup described in the issue. Check whether updating the AspectInjector dependency to 2.7 resolves the failure, then verify that editing a string during a debug run with allureStepAttribute allows execution to continue.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
testing-qa
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.