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.

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

chore(web): re-establish BrowserStack testing for legacy browser support #11501

Open
jahorton opened this issue May 23, 2024 · 2 comments · May be fixed by #11845
Open

chore(web): re-establish BrowserStack testing for legacy browser support #11501

jahorton opened this issue May 23, 2024 · 2 comments · May be fixed by #11845
Assignees
@jahorton
Labels
chore web/
Milestone
19.0

Comments

@jahorton
Copy link
Contributor

Note that at this stage, we have not yet established BrowserStack configs as per #11404 (comment) for nightly testing.

Extracted from #11300. Our use of the new @web/test-runner engine for automated Browser testing currently utilizes playwright, which exclusively tests against current browsers. As discussed in other channels, the long-term plan is to establish nightly tests on BrowserStack to act as 'canary testing' against issues with legacy browser support. (This way, they only run once a day, preventing our generally more-frequent PR test builds from being subjected to the flakiness we've occasionally seen when utilizing BrowserStack.)
@jahorton jahorton added this to the A18S3 milestone May 23, 2024
@jahorton jahorton self-assigned this May 23, 2024
@mcdurdin mcdurdin modified the milestones: A18S3, A18S4 May 26, 2024
@jahorton jahorton mentioned this issue Jun 10, 2024
Closed
@jahorton jahorton linked a pull request Jun 21, 2024 that will close this issue
Open
@darcywong00 darcywong00 modified the milestones: A18S4, A18S5 Jun 21, 2024
@darcywong00 darcywong00 modified the milestones: A18S5, A18S6 Jul 8, 2024
@darcywong00 darcywong00 modified the milestones: A18S6, A18S7 Jul 19, 2024
@darcywong00 darcywong00 modified the milestones: A18S7, A18S8 Aug 2, 2024
@darcywong00 darcywong00 modified the milestones: A18S8, A18S9 Aug 17, 2024
@jahorton
Copy link
Contributor Author

A possible alternative strategy:

It is relatively easy to download older versions of Chromium and test on those -- which I think would be sufficient. That then resolves the need to drag in 5,000 new lines of dependencies into package-lock.json and probably removes most of our BrowserStack requirement altogether?

by @mcdurdin in #11845 (comment)

Especially if we can find a similar route for WebKit, we may be better off doing a round or two of manual testing against these older versions every once in a while.

@mcdurdin
Copy link
Member

Especially if we can find a similar route for WebKit, we may be better off doing a round or two of manual testing against these older versions every once in a while.

TBH I am less concerned about WebKit. We have older devices we can test with for Safari and the user base for old devices on those platforms is much smaller.

@darcywong00 darcywong00 modified the milestones: A18S9, A18S10 Aug 31, 2024
@mcdurdin mcdurdin modified the milestones: A18S10, A18S19 Sep 2, 2024
@mcdurdin mcdurdin modified the milestones: A18S19, 19.0 Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jahorton jahorton

Labels
chore web/
Projects
Keyman
Status: No status
Milestone
19.0
Development

Successfully merging a pull request may close this issue.

chore(web): enable testing against legacy devices via BrowserStack keymanapp/keyman
3 participants
@mcdurdin @darcywong00 @jahorton