xbehave.net icon indicating copy to clipboard operation
xbehave.net copied to clipboard

Published 20 hours ago • verified publisher icon adamralph

ITestOutputHelper does not work in constructors/dispose or Teardown() when test-class contains xbehave-Scenarios

Open Jazzman82 opened this issue 5 years ago • 11 comments

Is it possible to add the ITestOutputHelper to those artifacts? It always says that there is no active test-case, but it should be possible as constructor/dispose and Teardown are test-case specific.

Jazzman82 avatar May 19 '19 12:05 Jazzman82

Hi @Jazzman82 thanks for raising this. I've successfully reproduced the problem.

The good news is that I currently have some work in progess which should fix this.

adamralph avatar May 19 '19 13:05 adamralph

Cool! So I will switch to patience-mode ;)

Jazzman82 avatar May 20 '19 11:05 Jazzman82

@adamralph Just ran into this myself, as I re-used a helper-method that writes to the ITestOutputHelper in a Teardown method, so I just wanted to check what the expectations are on this issue? Anything I can do to help out?

redoz avatar Apr 14 '20 17:04 redoz

I have the same issue. Any progress on this?

Andras-Csanyi avatar Sep 16 '20 13:09 Andras-Csanyi

@SayusiAndo unfortunately I have had no time to work on this.

adamralph avatar Sep 17 '20 18:09 adamralph

@adamralph No worries. I could solve it, unfortunately I had to drop xBehave.

Andras-Csanyi avatar Sep 17 '20 19:09 Andras-Csanyi

Any updates on this issue, would be great to be able to use ITestOutputHelper with xBehave

Eklange avatar Nov 25 '20 07:11 Eklange

I'm not aware of any progress since my last comment.

Anything I can do to help out?

@redoz PR's are always welcome. 🙂

adamralph avatar Nov 26 '20 09:11 adamralph

@adamralph Is #566 on hold waiting for xunit3?

redoz avatar Nov 26 '20 12:11 redoz

Is #566 on hold waiting for xunit3?

@redoz no, it's not waiting for xunit3. It's something I started a while back, but didn't have time progress with any further.

That said, I'm not entirely sure if it's worth trying to get that all done (I'm not entirely sure where it's leading TBH) or whether it's worth just leaving xbehave 2.x as-is and waiting for xunit 3. Because xunit 2 was so different to xunit 1, xbehave 2 was a complete re-write, so it may be the same for xbehave 3.

adamralph avatar Nov 26 '20 15:11 adamralph

@adamralph Yeah my impression was that doing significant work with xunit2 internals would be wasted effort as soon as xunit3 is released, so I'm looking for quick wins, and will see if the new version offers what I need before starting to extend it.

redoz avatar Nov 26 '20 16:11 redoz