test: add component view tests for Predict feature (PredictFeed + PredictMarketDetails)

[racitores]

Summary

First component view tests for the Predict feature area (MMQA-1529). Tests use Engine spies and real user interactions — no mocked hooks or selectors — following the integration-test doctrine: each test models a complete user journey, not an isolated unit behavior.

Infrastructure added

File	Purpose
tests/component-view/presets/predict.ts	State preset with predictTradingEnabled remote feature flag, PredictController state, PreferencesController.privacyMode, and TransactionController
tests/component-view/renderers/predict.tsx	renderPredictFeedView and renderPredictFeedViewWithRoutes, wrapped with QueryClientProvider (required by PredictBalance which uses @tanstack/react-query)
tests/component-view/renderers/predictMarketDetails.tsx	renderPredictMarketDetailsView and renderPredictMarketDetailsViewWithRoutes with initialParams support for route params
tests/component-view/fixtures/predict.ts	Shared MOCK_PREDICT_MARKET fixture used across both test files
app/components/UI/Predict/Predict.testIds.ts	Added PredictSearchSelectorsIDs (SEARCH_BUTTON, CLEAR_BUTTON, ERROR_STATE) and getPredictSearchSelector.resultCard(index) helper; all raw strings replaced with constants
tests/component-view/mocks.ts	Updated to support Predict engine context

PredictFeed tests (12)

• Search overlay opens when the user presses the search icon
• getMarkets called with the debounced typed query
• Search overlay closes when the user presses Cancel
• Clear button hides after user clears the input
• No-results message includes the typed query
• Data completeness: result card shows title + Yes/No tokens after getMarkets resolves
• Tapping a result card navigates to market details
• Back button navigates to wallet
• Balance card renders and getBalance is called on mount
• Add Funds triggers trackGeoBlockTriggered with attemptedAction: deposit
• Error state shown when all getMarkets retries fail
• Retry press calls getMarkets again after an error

PredictMarketDetails tests (5)

• getMarket called with marketId from route params on mount
• Data completeness: title + Yes/No bet buttons visible after getMarket resolves
• Pressing a bet button triggers trackGeoBlockTriggered while ineligible
• trackMarketDetailsOpened called after market and positions load
• Back button navigates to Predict root

Key implementation constraints

• The main feed (PagerView + FlashList) never renders in the test environment — it is gated by {layoutReady && <PredictFeedTabs />} and layoutReady stays false without native layout events. Tests focus on the search overlay which does render.
• Market card navigation targets Routes.PREDICT.ROOT (nested navigator), not MARKET_DETAILS directly.
• PredictBalance requires QueryClientProvider; renderer wraps with { retry: false } to surface errors immediately.

Test plan

yarn jest -c jest.config.view.js PredictFeed.view.test PredictMarketDetails.view.test --runInBand --silent --coverage=false

• All 17 tests pass
• No ESLint errors (yarn eslint app/components/UI/Predict/views/**/*.view.test.tsx)

🤖 Generated with Claude Code

---

Note

Low Risk
Low risk: changes are primarily test-only infrastructure plus refactors of testID strings in Predict UI components/tests. Main risk is breaking existing E2E/unit tests that rely on previous hard-coded selector strings.

Overview
Adds component view tests for Predict. Introduces new Predict component-view test suites for PredictFeed and PredictMarketDetails that validate real user flows (search, navigation, balance loading, error/retry) via Engine.context.PredictController spies.

Builds supporting test infrastructure and normalizes selectors. Adds Predict-specific component-view renderers, Redux state preset, and a shared MOCK_PREDICT_MARKET fixture; extends component-view Engine mocks with a stubbed PredictController. Updates PredictFeed and multiple unit tests to replace hard-coded testID strings with new constants/helpers in Predict.testIds.ts (feed/search/market-details selectors, skeleton/empty-state IDs).

^{Written by Cursor Bugbot for commit 8ba8bca. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[caieu]

LGTM

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokePredictions
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 90%

click to see 🤖 AI reasoning details

E2E Test Selection:
This PR contains test infrastructure improvements for the Predict (Predictions) feature:

1. Test ID Refactoring: The changes in Predict.testIds.ts add new centralized selector IDs and helper functions for dynamic test ID generation. This improves test maintainability but doesn't change any functional behavior.

2. Component Changes: The only app code change is in PredictFeed.tsx, which replaces hardcoded test ID strings with centralized selector constants. This is a pure refactoring with no logic changes.

3. Unit Test Updates: Both PredictFeed.test.tsx and PredictMarketDetails.test.tsx are updated to use the new centralized selectors instead of hardcoded strings.

4. New Component View Tests: New test files (PredictFeed.view.test.tsx, PredictMarketDetails.view.test.tsx) are added for better test coverage.

5. Test Infrastructure: New files in tests/component-view/ add fixtures, presets, renderers, and mocks specifically for Predict component testing.

Since all changes are confined to the Predictions feature (test IDs and test infrastructure), only SmokePredictions is needed to verify the Predictions functionality still works correctly. The changes are low risk as they are primarily test-related with no functional changes to the app logic.

Per the tag description, SmokePredictions tests the Polymarket prediction market integration including opening positions, cashing out, claiming winnings, and the Positions/Activities tabs - which aligns with the components being modified (PredictFeed, PredictMarketDetails).

Performance Test Selection:
These changes are purely test infrastructure improvements (test ID refactoring, new unit tests, test fixtures/mocks). There are no changes to UI rendering, data loading, state management, or any code paths that would affect app performance. The only app code change is replacing hardcoded test ID strings with centralized constants in PredictFeed.tsx, which has zero performance impact.

View GitHub Actions results

[github-actions]

⚠️ E2E Fixture Validation — Structural changes detected

Category	Count
New keys	68
Missing keys	11
Type mismatches	0
Value mismatches	7 (informational)

The committed fixture schema is out of date. To update, comment:

@metamaskbot update-mobile-fixture

View full details | Download diff report

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[caieu]

LGTM