Skip to content

CCCT-2710: Set New Backup Code screen - #3886

Open
shubham1g5 wants to merge 3 commits into
ccct-2709_confirm_backup_code_profilefrom
ccct-2710-set_new_backup_code
Open

CCCT-2710: Set New Backup Code screen#3886
shubham1g5 wants to merge 3 commits into
ccct-2709_confirm_backup_code_profilefrom
ccct-2710-set_new_backup_code

Conversation

@shubham1g5

@shubham1g5 shubham1g5 commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Product Description

https://dimagi.atlassian.net/browse/CCCT-2710

Screen_recording_20260828_144302.mp4

Review Commit by Commit

Safety Assurance

Locally tested end to end and limited impact radius.
Test Coverage

Labels and Review

  • Do we need to enhance the manual QA test coverage ? If yes, RELEASES.md is updated accordingly
  • Does the PR introduce any major changes worth communicating ? If yes, RELEASES.md is updated accordingly
  • Risk label is set correctly
  • The set of people pinged as reviewers is appropriate for the level of risk of the change

@shubham1g5
shubham1g5 marked this pull request as draft August 27, 2026 11:57
@shubham1g5
shubham1g5 force-pushed the ccct-2710-set_new_backup_code branch from f9114bc to 6f7d266 Compare August 27, 2026 11:59
@codecov

codecov Bot commented Aug 27, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 33.20%. Comparing base (44b4060) to head (6f7d266).

Additional details and impacted files
@@                             Coverage Diff                             @@
##             ccct-2709_confirm_backup_code_profile    #3886      +/-   ##
===========================================================================
+ Coverage                                    33.14%   33.20%   +0.06%     
- Complexity                                    5906     5921      +15     
===========================================================================
  Files                                         1004     1004              
  Lines                                        59564    59626      +62     
  Branches                                      7124     7129       +5     
===========================================================================
+ Hits                                         19740    19798      +58     
- Misses                                       37575    37577       +2     
- Partials                                      2249     2251       +2     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@shubham1g5
shubham1g5 force-pushed the ccct-2710-set_new_backup_code branch 3 times, most recently from 6263093 to 981d926 Compare August 28, 2026 09:14
@shubham1g5
shubham1g5 marked this pull request as ready for review August 28, 2026 09:29
@shubham1g5
shubham1g5 requested review from a team and OrangeAndGreen and removed request for a team August 28, 2026 09:32
shubham1g5 and others added 3 commits August 28, 2026 17:04
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Full implementation of the set-new-backup-code screen: both code and confirm fields
visible, validation for match and 6-digit length, biometric unlock via
PersonalIdUnlocker.ALWAYS before submission, setRecoveryPin API call, pin stored
on success with a success toast, and popBackStack to profile on completion.
Also adds personalid_backup_code_changed_success and personalid_set_new_backup_code_title
strings in all supported languages (es, fr, ha, hi, lt, no, pt, sw, ti).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Robolectric tests covering: initial UI state (confirm layout visible, button
disabled), validation (match/mismatch, length guard, error visibility), successful
save (navigates to profile, shows toast, stores updated pin), network error (inline
error shown, stays on screen), and unlock failure (no API call, stays on screen).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@shubham1g5
shubham1g5 force-pushed the ccct-2710-set_new_backup_code branch from 981d926 to 4a34cd2 Compare August 28, 2026 11:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant