Youssef Victor
Youssef Victor
I think @Evangelink is referring to some code that manually altered stack traces back in MSTest 3 that was removed in 4.x (https://github.com/microsoft/testfx/pull/6171)
> I would prefer to have the class disappear and replaced with proper specialized context. As we discussed in the past the information available at each "step" is/should be widely...
I will consider adding in 4.1 as experimental API.
@copilot Create new Azure Pipeline that runs the new sample, and publishes test results.
Which .NET SDK version are you using currently? This was fixed previously in https://github.com/NuGet/NuGet.Client/pull/6458
@nightowl286 Sorry for getting back to you late. If you set `true`, I don't see why would IsPackable not be set to false by default. Can you provide [binlogs](https://aka.ms/binlog) before...
I'm not able to reproduce. @nohwnd Can you try on your side to see if you can repro please?
I'm not sure why I wasn't able to repro, but given the binlogs, this is a VSTest regression. The packaging is wrong. `buildMultiTargeting` is intended to be for "outer" builds...
@nohwnd With net10, the NuGet does an additional check for `IsTestingPlatformApplication`. Probably the read that NuGet does is done *early* before we set back `IsTestingPlatformApplication` to false.
With the current design of `TestMethodAttribute` where `Execute` only accepts `ITestMethod`, it might not be easy for us to flow the cancellation token to `TestMethodAttribute`. I think it might be...