-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
Fix template tests to run in CI #46430
Comments
* Version Bumps * Run with `Test: Windows Server x64` * Install Playwright in CI * Add running playwright locally instructions * Test Cleanup * Remove Selenium * Prebuild for Playwright install * Update default-build.yml * Update default-build.yml * Update default-build.yml * Update default-build.yml * Update default-build.yml * Playwright install in test * New template test pipeline * Update components-e2e-tests.yml * Update components-template-tests.yml * Update components-e2e-tests.yml * Update components-e2e-tests.yml * Update components-e2e-tests.yml * Update components-template-tests.yml * Update components-e2e-tests.yml * Update components-e2e-tests.yml * Update components-e2e-tests.yml * Revert new pipeline changes * RestoreAdditionalProjectSources * Update Templates.Blazor.Tests.csproj * PR Feedback * RunBlazorPlaywrightTemplateTests * Socket logic * Fixed socket wait logic Fixes #30761 * Remove redundant process wait for exit We're already in the `Exited` Event: There are two ways of being notified when the associated process exits: synchronously and asynchronously. Synchronous notification means calling the WaitForExit method to block the current thread until the process exits. Asynchronous notification uses the Exited event, which allows the calling thread to continue execution in the meantime. In the latter case, EnableRaisingEvents must be set to true for the calling application to receive the Exited event. https://learn.microsoft.com/dotnet/api/system.diagnostics.process.exited?view=net-7.0 * Update BlazorWasmTemplateTest.cs * Update Templates.Blazor.Tests.csproj * Revert App.Ref, add src in props * Config updates * Update RequiresDelayedBuildProjects.props * Update Templates.Blazor.Tests.csproj * Skip failing tests * Add #46430 * Update Templates.Blazor.Tests.csproj * Update BlazorWasmTemplateTest.cs * Update BlazorWasmTemplateTest.cs --------- Co-authored-by: William Godbe <wigodbe@microsoft.com>
Fixed by #45682 |
We missed one: aspnetcore/src/ProjectTemplates/test/Templates.Blazor.Tests/BlazorWasmTemplateTest.cs Lines 62 to 65 in f9121bc
We also skip the only other Playwright test in the entire assembly: aspnetcore/src/ProjectTemplates/test/Templates.Blazor.Tests/BlazorWasmTemplateTest.cs Lines 26 to 28 in f9121bc
That issue is at least open, but it says the test is "Quarantined" when in fact it's really skipped. |
Resolved by #54606 |
Following tests are failing in the CI only (works fine locally), seems to be due to searching for the
StaticFiles
dependency. Unclear what exactly is pulling this dependency.BlazorWasmHostedTemplate_Works
BlazorServerTemplate_IdentityWeb_BuildAndPublish
BlazorWasmHostedTemplate_IndividualAuth_Works_WithLocalDB
BlazorWasmHostedTemplate_IndividualAuth_Works_WithOutLocalDB
The text was updated successfully, but these errors were encountered: