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

Ensure all E2E tests pass in Chromium's headless="new" mode #9482

Open
jcfranco opened this issue May 31, 2024 · 0 comments
Open

Ensure all E2E tests pass in Chromium's headless="new" mode #9482

jcfranco opened this issue May 31, 2024 · 0 comments
Labels
0 - new New issues that need assignment. epic Large scale issues to be broken up into sub-issues and tracked via sprints and/or project. estimate - 13 Requires planning and input from team, consider smaller steps. p - high Issue should be addressed in the current milestone, impacts component or core functionality testing Issues related to automated or manual testing.
Milestone
2025-04-29 - Apr ...

Comments

@jcfranco
Copy link
Member

Priority impact

p - high

Test type

E2E

Which Component(s)

All E2E test suites

Unstable Tests

No response

Test error, if applicable

No response

PR skipped, if applicable

No response

Additional Info

Results from E2E tests will differ between headful and headless mode (rendering engine is different between them).

We need to start updating tests gradually to pass with Chrome's new headless mode, which shares the same engine as headful . #8820 tested this new mode and resulted in a lot of failures. Some were caused by setup or interactions and not necessarily because tests are incorrect.
@jcfranco jcfranco added testing Issues related to automated or manual testing. 0 - new New issues that need assignment. epic Large scale issues to be broken up into sub-issues and tracked via sprints and/or project. needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. labels May 31, 2024
@github-actions github-actions bot added the p - high Issue should be addressed in the current milestone, impacts component or core functionality label May 31, 2024
@jcfranco jcfranco added estimate - 13 Requires planning and input from team, consider smaller steps. p - high Issue should be addressed in the current milestone, impacts component or core functionality and removed p - high Issue should be addressed in the current milestone, impacts component or core functionality labels May 31, 2024
@geospatialem geospatialem added this to the 2025-04-29 - Apr Release milestone Aug 7, 2024
@geospatialem geospatialem removed the needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. label Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0 - new New issues that need assignment. epic Large scale issues to be broken up into sub-issues and tracked via sprints and/or project. estimate - 13 Requires planning and input from team, consider smaller steps. p - high Issue should be addressed in the current milestone, impacts component or core functionality testing Issues related to automated or manual testing.
Projects
None yet
Milestone
2025-04-29 - Apr Milestone
Development

No branches or pull requests
2 participants
@jcfranco @geospatialem