You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* 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 <[email protected]>
3.`dotnet test .\Templates.Blazor.Tests.csproj` with optional `--filter` arg to run a specific test.
79
+
80
+
The requisite browsers should be automatically installed. If you encounter browser errors, the browsers can be manually installed via the following script, replacing `[TFM]` with the current target TFM (ex. `net8.0`).
81
+
82
+
```cmd
83
+
.\bin\Debug\[TFM]\playwright.ps1 install
84
+
```
85
+
74
86
#### Conditional tests & skipping test platforms
75
87
76
88
Individual test methods can be decorated with attributes to configure them to not run ("skip running") on certain platforms. The `[ConditionalFact]` and `[ConditionalTheory]` attributes must be used on tests using the skip attributes in order for them to actually be skipped:
0 commit comments