Brad Wilson
Brad Wilson
> I'll check with @drognanar what the VS behavior in this case I can see that Test Explorer is doing what I want (leaving the test as not run), and...
I use .NET SDK 8. If there are new nullability rules added in 9 they may be triggering. Try adding a global.json.
I'm building with `9.0.100-preview.7.24407.12` and I don't see any nullability issues. I do see a bunch of new instances of `NETSDK1215` and `NU1903`.
Getting past the NuGet warnings, I see a lot of new analyzers that are triggering (`1705 error(s) and 3470 warning(s)`), so you're going to be best off just using `global.json`...
FYI, I have fixed up the compiler issues (at least as much as I'm seeing with `9.0.100-preview.7.24407.12`) and pushed up the changes. You should be able to pull and then...
Obviously it remains to be seen if/how other third party runners (Rider/Resharper/CodeRush/etc.) adopt support for Microsoft.Testing.Platform. The only UX experiences I have right now are: 1. Test Explorer (the experimental...
> I was wondering if this state should be returned as new discovery state. FWIW, our `ITestCaseDiscovered` message does include `Explicit` in the metadata, so we would be able to...
So this would be an execution result, not a discovery result, correct?
I disagree with @wiz0u, I'd rather see the ugly HTML (so people know something is there, even if it's not currently rendered properly) than to have it hidden away, which...
Sorry for the delay, I thought I had already left a comment here but I must not have submitted it. ☹️ The fix provided here is very focused on specifically...