test: move challenge title coverage to client by Sembauke · Pull Request #68056 · freeCodeCamp/freeCodeCamp · GitHub
Skip to content

test: move challenge title coverage to client#68056

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

test: move challenge title coverage to client#68056
Sembauke wants to merge 1 commit into
freeCodeCamp:mainfrom
Sembauke:test/move-challenge-title-coverage-to-client

Conversation

@Sembauke

Copy link
Copy Markdown
Member

Checklist:

This moves the challenge title rendering coverage out of Playwright and into the component test. The client test now covers the title, completed and incomplete pass icon states, and the translation-pending link, so the old browser spec is no longer carrying component-level assertions.

Keeping this in the client test layer makes the remaining Playwright suite a little smaller and keeps browser coverage focused on flows that actually need the full app stack.

@Sembauke Sembauke requested review from a team as code owners June 18, 2026 11:27
@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 18, 2026
@majestic-owl448 majestic-owl448 added status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. MERGE CONFLICT! To be applied to PR's that have a merge conflict and need updating labels Jun 18, 2026
@Sembauke Sembauke force-pushed the test/move-challenge-title-coverage-to-client branch from c49275b to 2655755 Compare June 24, 2026 14:31
@Sembauke Sembauke added status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. 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. and removed status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. 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. MERGE CONFLICT! To be applied to PR's that have a merge conflict and need updating labels Jun 24, 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