Skip to content

Evaluate the impact of Chromium Edge on SignalR browser-based testing. #18524

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.

Sign up for GitHub

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

Jump to bottom
Open
analogrelay opened this issue Jan 22, 2020 · 2 comments
Open

Evaluate the impact of Chromium Edge on SignalR browser-based testing. #18524

analogrelay opened this issue Jan 22, 2020 · 2 comments
Labels
affected-very-few This issue impacts very few customers area-signalr Includes: SignalR clients and servers severity-nice-to-have This label is used by an internal tool task
Milestone
Backlog

Comments

@analogrelay
Copy link
Contributor

Our browser-based tests use Karma's edge launcher, and Sauce Labs when running in the cloud. I expect that is launching Edge Legacy, rather than the Chromium-based Edge, but we should check that and look at splitting our testing so we're testing both Edge Legacy and Edge Chromium.
@analogrelay analogrelay added the area-signalr Includes: SignalR clients and servers label Jan 22, 2020
@analogrelay analogrelay mentioned this issue Jan 22, 2020
Merged
@analogrelay analogrelay added this to the Next sprint planning milestone Jan 24, 2020
@analogrelay
Copy link
Contributor Author

Also, we can probably run Edge tests on AzDO now since Chromium Edge probably supports headless!

We're ok with shifting Edge Legacy testing to Sauce Labs.

@analogrelay
Copy link
Contributor Author

Pre-planning notes: Punty punt. We have Chromium coverage already.

@BrennanConroy BrennanConroy added affected-very-few This issue impacts very few customers severity-nice-to-have This label is used by an internal tool labels Nov 11, 2020 — with ASP.NET Core Issue Ranking
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affected-very-few This issue impacts very few customers area-signalr Includes: SignalR clients and servers severity-nice-to-have This label is used by an internal tool task
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
2 participants
@analogrelay @BrennanConroy