Repository navigation
Conversation
Signed-off-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
Signed-off-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
A retry after SumSub has already submitted documents must show the retry screen and must not launch SumSub again.
Smart E2E Test SelectionSelected E2E tags: No E2E tests selected AI Confidence: 96 E2E reasoningExpand to readBoth changed files are Jest component-view test infrastructure. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## fix/TRAM-4291 #39659 +/- ##
================================================
Coverage ? 87.89%
================================================
Files ? 8190
Lines ? 240815
Branches ? 61179
================================================
Hits ? 211665
Misses ? 16494
Partials ? 12656 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
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. |
PR template — items to address before "Ready for review"Warnings — informational, address before merging:
See docs/readme/ready-for-review.md for the full Definition of Ready for Review. |
|
|
Folded into #39262, which now carries these tests. |



Description
A KYC
retryafter a proof-of-address upload was reopening SumSub instead of the retry screen. The provider flow stayssubmittedafter the first upload, so that retry was treated as another identity check. Combined with the two-minute resume after an app restart, SumSub kept opening again.#39497 sends every
retryto the retry screen, whatever the provider flow status is. Try again is still the only way back into SumSub.This adds a component-view test of the full path: submit, then pending, then a retry status. It checks that the retry screen is shown and that SumSub launches once. A second case reopens onboarding on that same retry and checks that SumSub does not launch again. The second case reopens the money entry on that same retry and submitted provider flow. It does not cover the two-minute post-unlock resume timer.
Test layer placement
Component-view. The bug is which screen appears after the KYC session status changes, through the real VBA onboarding navigator and Redux. Engine is the only mock. The funnel helper already has a unit test; this covers the screens that helper does not.
Changelog
CHANGELOG entry: null
Related issues
Refs: #39497
Manual testing steps
N/A. Test-only change.
Screenshots/Recordings
Before
N/A
After
N/A
Pre-merge author checklist
Performance checks (if applicable)
trace()for usage andaddTokenfor an exampleFor performance guidelines and tooling, see the Performance Guide.
Pre-merge reviewer checklist