chore: Bump to 9.0.200

[MartinZikmund]

GitHub Issue (If applicable): closes #

PR Type

What kind of change does this PR introduce?

What is the current behavior?

What is the new behavior?

PR Checklist

Please check if your PR fulfills the following requirements:

• Docs have been added/updated which fit documentation template (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Validated PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Associated with an issue (GitHub or internal) and uses the automatic close keywords.
• Commits must be following the Conventional Commits specification.

Other information

Internal Issue (If applicable):

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19592/index.html

[unodevops]

🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-19592/index.html

[unodevops]

⚠️⚠️ The build 156172 has failed on Uno.UI - CI.

[unodevops]

⚠️⚠️ The build 156202 has failed on Uno.UI - CI.

[ajpinedam]

Looks good

[unodevops]

⚠️⚠️ The build 156251 has failed on Uno.UI - CI.

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19592/index.html

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19592/index.html

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19592/index.html

[unodevops]

🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-19592/index.html

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19592/index.html

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19592/index.html

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19592/index.html

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19592/index.html

[unodevops]

🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-19592/index.html

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19592/index.html

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19592/index.html

[unodevops]

🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-19592/index.html

[Youssef1313]

@jeromelaban I assume this is the update you referred to for fixing Wasm UI tests, but I see the test host is still crashing here.

Test Run Aborted.
Total tests: Unknown
     Passed: 13
     Failed: 6
    Skipped: 61
 Total time: 3.9866 Minutes

So the update doesn't seem to fix it?

[jeromelaban]

No, and it seems to have started from #18267, curiously. It may not be the PR itself, could also be and change in the hosted agents, somehow.

[jeromelaban]

I rebuilt the merge commit before #18267, and it's building and testing properly. This means that there's something in that PR that broke the app and/or the test engine, somehow. I'm still trying to find out what.

[unodevops]

🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-19592/index.html

[jeromelaban]

So it looks like the --filter syntax has changed and that there were many more tests that were running that should have been. I've adjusted a bit the syntax, and it's not failing anymore.

There's another problem related to the default size of the browser, but this is related to the update of selenium/chromium, and that will be fixed in a separate change.

[Youssef1313]

@jeromelaban Hmm, I'm not aware of any changes in filter syntax. If you are referring to the Namespace part (which you changed to FullyQualifiedName instead), it's supposed to work as the generator defines that property:

uno/src/SamplesApp/SamplesApp.UITests.Generator/CategoryBucketGenerator.cs

Line 70 in 6a2b548

builder.AppendLineIndented($"[global::NUnit.Framework.Property(\"Namespace\", \"{type.ContainingNamespace}\")]");

But yeah, with my PR to migrate to MTP, I noticed there that something with regards the filter feels like it's not working as expected.

[unodevops]

🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-19592/index.html

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19592/index.html

[jeromelaban]

@Youssef1313 Given my last change, which rollback to Namespace in the filter, the build is now failing again.

[Youssef1313]

It might be worth reporting to NUnit then.

[Youssef1313]

@jeromelaban fwiw, filtering using Namespace is done also for iOS and Android. It may be worth validating whether or not it's working as intended.