Skip to content

test: move flash rendering coverage to client#68240

Open
Sembauke wants to merge 1 commit into
freeCodeCamp:mainfrom
Sembauke:test/move-flash-rendering-coverage-to-client
Open

test: move flash rendering coverage to client#68240
Sembauke wants to merge 1 commit into
freeCodeCamp:mainfrom
Sembauke:test/move-flash-rendering-coverage-to-client

Conversation

@Sembauke

Copy link
Copy Markdown
Member

Checklist:

This moves the mocked user-fetch-error flash rendering check from Playwright to flash.test.tsx. The client test covers rendering the flash message and dismissing it through the close button.

The settings night-mode and sound-mode flash checks stay in Playwright because they still prove the settings page interaction produces the visible flash.

@Sembauke Sembauke requested review from a team as code owners June 25, 2026 09:33
@github-actions github-actions Bot added platform: learn UI side of the client application that needs familiarity with React, Gatsby etc. scope: tools/scripts Scripts for supporting dev work, generating config and build artifacts, etc. labels Jun 25, 2026
@moT01 moT01 added the status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. label Jun 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

platform: learn UI side of the client application that needs familiarity with React, Gatsby etc. scope: tools/scripts Scripts for supporting dev work, generating config and build artifacts, etc. status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants