Feat:Add page-level composition tests for landing, streams, analytics, and stream-detail pages /page tests 765 766 770 771 - #881
Merged
Austinaminu2 merged 4 commits intoSep 28, 2026
Conversation
…eam/[id]/page.tsx
|
@Barbie-Dev Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Barbie-Dev
had a problem deploying
to
staging
September 28, 2026 00:14 — with
GitHub Actions
Failure
This branch had an error being deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds page-level composition tests for four pages that lacked
coverage at the composition level. Each test file follows the established
pattern from the existing settings page test — module-level vi.mock stubs
for hooks and heavy child components, isolated describe blocks per UI
state, and no dependency on real wallets, contracts, or network calls.
Changes
__tests__/pages/app/landing.test.tsx(issue #765)Tests that
app/page.tsxrenders all seven landing sections together(LandingHeader, Hero, Features, HowItWorks, UseCases, CTA, Footer) and
that they appear in the correct document order.
__tests__/pages/app/streams.test.tsx(issue #766)Tests that
app/app/streams/page.tsxrenders the wallet gate, pageheader, Active/Archived tab switcher, all filter controls (search input,
token pills, status pills, sort select), the bulk-select toggle
(enabled/disabled based on stream count), and the VirtualStreamList vs
EmptyStreams states — all wired to a mocked
useStreams.__tests__/pages/app/analytics.test.tsx(issue #770)Tests that
app/app/analytics/page.tsxrenders all four stat cards withloading skeletons while data is resolving (regression guard for fix #674),
correct values from a mocked streams dataset, the AnalyticsCharts
component, and the Network context card with token badges.
__tests__/pages/app/stream-detail.test.tsx(issue #771)Tests that
app/app/stream/[id]/page.tsxrenders the loading skeleton,the not-found state for a bad ID, and the full composition for a found
stream (status badge, unlock counter, progress bar, unlock chart,
timeline, details section, share button). Also covers party-specific
actions: sender sees Cancel and Duplicate buttons, recipient sees Withdraw,
and unauthenticated visitors see the connect-wallet prompt.
Closes #765
Closes #766
Closes #770
Closes #771