test: MMQA - 1711 - [Mobile] Update Predict e2e tests to enable features that were disabled due to feature flag updates#29154
Conversation
|
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. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #29154 +/- ##
==========================================
+ Coverage 81.86% 81.88% +0.01%
==========================================
Files 5255 5271 +16
Lines 138980 139465 +485
Branches 31518 31688 +170
==========================================
+ Hits 113774 114198 +424
- Misses 17465 17511 +46
- Partials 7741 7756 +15 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
AI PR Analysis🚫 Merge safe: false | 🟠 Risk: high
AI analysis did not complete. Manual review recommended. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit c564cee. Configure here.
cortisiko
left a comment
There was a problem hiding this comment.
@LeVinhGithub the PR looks good, but there are failing tests. can you have a look when you get a chance ?
🔍 Smart E2E Test Selection
click to see 🤖 AI reasoning detailsE2E Test Selection:
Tag selection rationale:
Performance Test Selection: |
|




Description
Brings Predict E2E test feature flag mocks into parity with production values.
Two remote feature flag overrides in predict smoke tests diverged from production after a feature flag registry sync (PR #28444). This PR aligns the mocks:
exploreSectionsOrder: Replaced the explicit section ordering arrays with{}in 4 predict smoke specs. On production this flag is empty; the app falls back to hardcoded defaults which produce the same layout. The Homepage component does not consume this flag at all — it only affects TrendingView/Explore, which these tests don't exercise.predictLiveSports: Added'nba'to the leagues list (now['nfl', 'nba']) to match production. This causes NBA markets (Spurs vs. Pelicans) to render viaPredictGameDetailsContent, which uses a different cash-out button test ID (predict-picks-cash-out-button-{positionId}). Updated thePredictDetailsPagepage object with a newtapGameCashOutButton(positionId)method and updatedpredict-cash-out.spec.tsto use it.Changelog
CHANGELOG entry: null
Related issues
Fixes: MMQA-1711
Manual testing steps
Feature: Predict E2E prod parity
Scenario: Cash out on NBA game market uses correct button
Scenario: Predict tests work without explicit exploreSectionsOrder
{}in all predict smoke specsScreenshots/Recordings
Before
N/A — test-only changes, no UI impact.
After
N/A — test-only changes, no UI impact.
Pre-merge author checklist
Pre-merge reviewer checklist
Note
Low Risk
Test-only changes that adjust feature-flag mocks and E2E selectors; low product risk, but could affect Predict smoke test stability if testIDs/position IDs drift.
Overview
Aligns Predict E2E remote feature-flag mocks with current production defaults by removing the
predictLiveSportsoverride fromremoteFeatureFlagPredictEnabled.Updates Predict smoke specs to interact with the game-details UI: adds a shared
SPURS_PELICANS_POSITION_ID, introducesPredictDetailsPage.tapGameCashOutButton(positionId)andtapGameBetYesButton(), and switches cash-out/position-opening tests to use the new testIDs for NBA/game markets.Reviewed by Cursor Bugbot for commit f452736. Bugbot is set up for automated code reviews on this repo. Configure here.