mirror of
https://github.com/Comfy-Org/desktop.git
synced 2026-11-04 23:47:43 +00:00
[GH-ISSUE #1179] [CI] Create playwright test expectation update script #325
Labels
No labels
area: desktop-app
Bounty
bug
bug-cop:answered
bug-cop:response-received
component: installer
component: preload
custom node
dependencies
Design
documentation
duplicate
enhancement
expected
frontend
good first issue
installation
Low-Priority
performance
Planned
platform: cross-platform
platform: windows
Potential Bug
Potential Bug
pull-request
question
refactor
Release
stale
User Support
V1
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/desktop#325
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @webfiltered on GitHub (May 27, 2025).
Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/1179
Frontend CI may be able to be copied over without much effort
┆Issue is synchronized with this Notion page by Unito
@robinjhuang commented on GitHub (May 29, 2025):
This Issues has been set to be bounty, here is the link on how to sign up for this bounty: https://comfyorg.notion.site/ComfyUI-Bounty-Tasks-1fb6d73d36508064af76d05b3f35665f or click here to sign up
@christian-byrne commented on GitHub (Jun 11, 2025):
"Frontend CI [workflow]" refers to https://github.com/Comfy-Org/ComfyUI_frontend/blob/main/.github/workflows/test-browser-exp.yaml
@christian-byrne commented on GitHub (Jun 11, 2025):
The workflow run Playwright tests and update snapshots then commits the updated expectations.
@Myestery commented on GitHub (Jun 14, 2025):
Hi @christian-byrne
I'm trying to work on this issue and have communicated internally with the team.
I'll like to know explicitly what needs to be done to the workflow so I can proceed with my solution
Does it suffice to just add playwright tests to the CI workflow?
@christian-byrne commented on GitHub (Jun 14, 2025):
Hi! For this, we want a workflow that can update the test screenshot expectations and then commit those updated screenshots to a PR. You can see in this example: https://github.com/Comfy-Org/ComfyUI_frontend/blob/main/.github/workflows/test-browser-exp.yaml that it works like: (1) we make a PR that changes behavior of playwright tests that use screenshots, (2) we add a specific label to the PR, (3) the workflow runs and commits the newly updated screenshot expections directly onto our PR.
You can also check in that (ComfyUI_frontend) repo to see past PRs that had the label applied and see the commit history to understand a bit more about the process.
@BenraouaneSoufiane commented on GitHub (Jun 19, 2025):
Hello, can I work on this for 250$?
@kevinpaik1 commented on GitHub (Jun 26, 2025):
@Myestery thank you for your contribution!
@Myestery commented on GitHub (Jun 26, 2025):
Glad I was able to help