Add screen smoke tests for the public-screens detail/feed/static screens
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- typescript
Research direction
Start by reading PR #28 and the existing public-screen smoke tests, then inspect apps/web/tests/test-utils.tsx for renderScreen(), mockOk(), and mockPaginated(). Add coverage for PersonDetail, TagDetail, both feeds, Volunteer, and Sponsor, asserting the listed load-bearing Display Rules; done means each screen has two or three smoke-test assertions and the test suite passes.
Written by the indexing model from the issue text.
Description
Context: PR #28 (feat/public-screens) shipped screen smoke tests for Home, ProjectsIndex, ProjectDetail, HelpWantedIndex — the screens with the most spec-bound Display Rules. The remaining screens were exercised only via the build + browser walkthrough, not unit tests.
Add smoke tests for:
-
PersonDetail— renders fullName + "Member since {month yyyy}" + projects list sorted by maintainer / joinedAt -
TagDetail— renders the three sections (Projects / Help-wanted / Members), hides Members oneventnamespace -
ProjectUpdatesFeed— renders cards reverse-chron, filtered empty state -
ProjectBuzzFeed— same shape, external-link headlines -
Volunteer— hero CTA toggles on auth state, live project count uses /api/projects?perPage=1 -
Sponsor— static content + copy-to-clipboard button
Each test: render with renderScreen() from apps/web/tests/test-utils.tsx, mock fetch with mockOk / mockPaginated, assert two or three load-bearing Display Rules from the spec.
Scoped small enough for a single follow-up PR.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 25
Contributor guide
No contributing guide indexed for this repository
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 CodeForPhilly/codeforphilly-ng
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
MarkdownEditor toolbar: use Radix Toolbar from radix-ui instead of the hand-rolled roving tabindex Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
All issues in CodeForPhilly/codeforphilly-ng
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mksglu/context-mode#1200 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jaegertracing/jaeger-ui#4506 ·
-
area:desktop area:ui bug platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anthropics/claude-code#96687 ·
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
AOSSIE-Org/DebateAI#582 · 2 comments ·