Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blazor Hybrid validation cases #39933

Closed
SteveSandersonMS opened this issue Feb 2, 2022 · 3 comments
Closed

Blazor Hybrid validation cases #39933

SteveSandersonMS opened this issue Feb 2, 2022 · 3 comments
Assignees
Labels
area-blazor Includes: Blazor, Razor Components feature-blazor-desktop This issue is related to Blazor Desktop
Milestone

Comments

@SteveSandersonMS
Copy link
Member

SteveSandersonMS commented Feb 2, 2022

This issue is to track creation of automated or CTI tests for Blazor Hybrid scenarios.

Target from Windows from Mac
Android dotnet/maui#4919 dotnet/maui#4925
iOS dotnet/maui#4921 dotnet/maui#4920
Mac dotnet/maui#4923 dotnet/maui#4924
WinUI dotnet/maui#4926 n/a
WinForms Some steps fail n/a
WPF dotnet/maui#4927 n/a

⌛ = No CTI steps yet prepared

TODO: Determine which of the above are supported. Some combinations might be publish-only without an accompanying developer experience (e.g., Linux CI might be able to publish with -r win-x64).

TODO: In each supported case, create and link to a CTI test that covers:

  • Creating the project
  • Core developer experience
    • Launching the app (e.g., in simulator/emulator where applicable)
    • Hot reload
    • Debugging
  • Core webview/Blazor-specific functionality
    • Consuming an RCL with components and static assets
    • Navigating between Blazor components and to external URLs
    • Event handling
    • File inputs
    • Unhandled exceptions
  • Publishing, and observing that the resulting app (including RCL assets, etc) does work

We may find that some of the core webview/Blazor-specific functionality can actually be covered by automated tests and hence is not needed in the CTI script.

@SteveSandersonMS SteveSandersonMS added area-blazor Includes: Blazor, Razor Components feature-blazor-desktop This issue is related to Blazor Desktop labels Feb 2, 2022
@SteveSandersonMS SteveSandersonMS added this to the 7.0-preview2 milestone Feb 2, 2022
@davidortinau
Copy link

davidortinau commented Feb 4, 2022

For .NET MAUI:

  • Mac as a target is not a supported scenario from Windows.
  • Windows as a target is not a supported scenario from Mac.
  • "from Linux" is not supported, though may work for Android

@SteveSandersonMS
Copy link
Member Author

Thanks @davidortinau. I've updated the matrix.

@SteveSandersonMS
Copy link
Member Author

@mkArtakMSFT FYI I've filed issues for all the other scenarios here, and am bumping this meta-issue forwards into 7.0 Preview 3.

My suggestion is we treat the need for coverage like this:

P1:

  • Android from Windows
  • iOS from Mac
  • iOS from Windows
  • macOS from Mac
  • WinUI
  • WPF

P2:

  • macOS from Windows (because mostly the tech will be covered by iOS from Windows)
  • Android from Mac (because mostly the tech will be covered by Android from Windows)

@ghost ghost locked as resolved and limited conversation to collaborators Jun 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components feature-blazor-desktop This issue is related to Blazor Desktop
Projects
None yet
Development

No branches or pull requests

3 participants