Youssef Victor

Looks like a problem in Playground default styles? https://github.com/unoplatform/Uno.Playground/blob/64c2ccfd3d10d8df0f68b7806f6ba17d6c4e79d7/src/Uno.Playground.Shared/DefaultStyles.xaml#L814 GitHubUno.Playground/DefaultStyles.xaml at 64c2ccfd3d10d8df0f68b7806f6ba17d6c4e79d7 · unoplatform/Uno.PlaygroundSource code for the Uno Gallery apps and Uno Playground (made in Wasm) - Uno.Playground/DefaultStyles.xaml at 64c2ccfd3d10d8df0f68b7806f6ba17d6c4e79d7...

@sakshi173  Does this look good to you? (CheckBox in progress)

@sakshi173 Yes, the PR https://github.com/unoplatform/Uno.Playground/pull/424 is not yet merged.

We will break the whole experience in favor of the new `dotnet test`. So closing out.

Re-opening to track breaking change of removing the old APIs.

``` failed RunAllTestsWithMixedTFMsWillProvideAdditionalInformationToTheDebugger (Row: 19, Every runner, Runner = net8.0, TargetFramework = net8.0, InIsolation, vstest.console = 17.6.2 [MostDownloaded], Testhost = 17.15.0-ci [Latest], MSTest = 3.9.3 [LatestStable]) (16s 791ms) Expected collection...

A better idea here is to make TestMethodIdentifierProperty required based on if it's needed or not. i.e, allow an extension to "ask" for it. Framework authors can then "omit" the...

Unlikely we will be able to take this in v2 due to NUnit/Expecto relying on this. Closing out for now.

I agree with @Evangelink. Changing the default of this flag is too breaking, and will be confusing because now the "default" behavior makes it that `Assert.Fail` and `Assert.Inconclusive` are the...

We need to discuss more if we need to take this break for v4 or postpone to v5 if it's going to be too hard for users. Alternative ideas: -...