[release/7.0.2xx] Backport Add Blazor SWA Baseline Mismatched Assets Logging #28883
Conversation
* Add Blazor AssetDifferencesDetails * Update AspNetSdkBaselineTest.cs For https://github.com/dotnet/sdk/issues/27346 * Spacing * Create blazor-swa-baseline-generation.md * PR Feedback * Remove instructions add script reference * Property level comparison * Added instructions * Update AspNetSdkBaselineTest.cs * Update AspNetSdkBaselineTest.cs (cherry picked from commit bacc17c)
TanayParikh
requested review from
captainsafia and
mkArtakMSFT
as code owners
|
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
|
@marcpopMSFT @dsplaisted where else do you believe we should backport this? Or maybe we handle it on a case-by-case basis? |
TanayParikh
added
the
Area-AspNetCore
|
Will this make the tests more stable? 7.0.1xx will be in support for ~18 months so anything that helps make codeflow PRs more reliable is worth taking. I've ported dozens of improvements to 6.0.1xx for test stability for similar reasons. |
This will have no impact on stability. The purpose of this change is to provide clarity on why the baseline tests failed (asset added/removed, or specific property changed), as well as steps to update the baselines should the change in fact be expected. Examples of what the error messages will now look like. Note, the test failures / instability caused by the baselines, aren't necessarily Blazor specific issues. The baselines act as a catch-all for issues across the stack. For instance, just the other day, the baselines caught #28796 (comment).
Will backport there as well. |
Backports #27542