Document how Playwright visual baselines are generated
Maintainers usually reply within 1 day
@joshfatoye0011-bit is already working on this.
Since Oct 16, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, markdown
- Domain
- documentation, testing
Research direction
Start with the Playwright section of docs/TESTING.md (around line 68), which currently only mentions npm run test:e2e:update, and read .github/workflows/update-snapshots.yml to see how the manual Update Playwright Snapshots workflow generates baselines. Done means TESTING.md explains when to regenerate baselines, how to trigger the workflow, and why Windows/macOS baselines should not be committed, and CONTRIBUTING.md links to that section.
Written by the indexing model from the issue text.
Description
Description
CI no longer regenerates screenshot baselines; they come from the manual Update Playwright Snapshots workflow, and CI skips screenshot assertions until baselines are committed. docs/TESTING.md still only says npm run test:e2e:update.
Location
docs/TESTING.md (Playwright section, ~line 68); .github/workflows/update-snapshots.yml; CONTRIBUTING.md.
Task
Explain when to regenerate baselines, how to run the workflow, and why baselines generated on Windows/macOS shouldn't be committed.
Acceptance criteria
- TESTING.md describes the workflow
- CONTRIBUTING links to it
Good for contributors because
Docs-only; helps every contributor touching UI.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 144
- Avg merge
- 9h 45m
- Merged PRs (30d)
- 74
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FlowwStar/FlowStar
-
Remove unused formatFee() from fee-utils.tsPossibly taken @jiangyuer018 claimed this 4 days ago. Openfrontend good first issue
Difficulty 1/5 Under an hour Newbie friendliness 92/100
FlowwStar/FlowStar#1039 · 3 comments ·
Maintainers usually reply within 1 day
-
frontend good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Add a timeout to the XLM price fetch in use-token-pricePossibly taken @Dekah101 claimed this 4 days ago. Openfrontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
FlowwStar/FlowStar#1037 · 1 comment ·
Maintainers usually reply within 1 day
-
frontend good first issue ux
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FlowwStar/FlowStar#1036 · 1 comment ·
Maintainers usually reply within 1 day
-
Add a request timeout to Horizon fetches in lib/stellar.tsPossibly taken @Ikechukwu-Patrick claimed this 4 days ago. Openfrontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
FlowwStar/FlowStar#1035 · 1 comment ·
Maintainers usually reply within 1 day
All issues in FlowwStar/FlowStar
Similar issues
-
level/task type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
wazuh/wazuh-dashboard-plugins#9508 ·
Maintainers usually reply within 1 day
-
Testnet EOL page links Zonescan mainnetPossibly taken @napelvs claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Azure-Samples/azure-search-openai-demo#3249 ·
Maintainers usually reply within 1 day
-
[Docs] docs/architecture.mermaid leaves out 21 of the 51 src/ directoriesPossibly taken @uyg7x claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
enhancement status:needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
dongdongbh/Mindwtr#1438 ·
Maintainers usually reply within 1 day