test: migrate test cases from enzyme to RTL

[psrigummadidala]

https://2u-internal.atlassian.net/browse/PROD-4397
Description:

This PR includes the following changes:

Upgraded React and React DOM from version 17 to 18.
Removed Enzyme and related dependencies (enzyme, enzyme-adapter-react-16, etc.).
Rewritten all unit tests using React Testing Library to align with React 18 best practices.
Ensured compatibility with concurrent features introduced in React 18.
Verified that all tests pass and application behavior remains consistent.
Why this change is necessary:

Enzyme does not support React 18 and is no longer actively maintained.

[openedx-webhooks]

Thanks for the pull request, @psrigummadidala!

This repository is currently maintained by @openedx/2u-phoenix.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Submit a signed contributor agreement (CLA)

⚠️ We ask all contributors to the Open edX project to submit a signed contributor agreement or indicate their institutional affiliation.
Please see the CONTRIBUTING file for more information.

If you've signed an agreement in the past, you may need to re-sign.
See The New Home of the Open edX Codebase for details.

Once you've signed the CLA, please allow 1 business day for it to be processed.
After this time, you can re-run the CLA check by adding a comment below that you have signed it.
If the CLA check continues to fail, you can tag the @openedx/cla-problems team in a comment for further assistance.

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[ankit-sonata]

@psrigummadidala Build is getting failed, Make sure the build should pass

[psrigummadidala]

Hi Ankith, Thanks for the update. I’ll look into the build issue right away and ensure it passes. I’ll keep you posted once it’s resolved . Best regards Padmasri.G

…

On Thu, Aug 21, 2025 at 12:34 AM ankit-sonata ***@***.***> wrote: *ankit-sonata* left a comment (openedx/frontend-app-support-tools#465) <#465 (comment)> @psrigummadidala <https://github.com/psrigummadidala> Build is getting failed, Make sure the build should pass — Reply to this email directly, view it on GitHub <#465 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BT7RJWSFUXQW2LUDSEWWL2T3OTBELAVCNFSM6AAAAACDHRTDM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMBXGY4DEMRRG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- *Padmasri Gummadidala* *Senior digital engineer* Employee of Sonata Software supporting 2U, LLC Vamsiram Suvarnadurga Tech Park, Gachibowli, Hyderabad, Telangana 500032, India Disclaimer: This message was sent by a contractor and may contain confidential or personal data. It does not create any binding obligation on behalf of 2U unless expressly confirmed in a formal agreement. If you are not the intended recipient, please notify the sender and delete this message immediately.

[ankit-sonata]

@psrigummadidala The build is failing due to commit lint fix them.

[codecov]

Codecov Report

❌ Patch coverage is 57.97101% with 29 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.49%. Comparing base (4e29750) to head (a920f66).

Files with missing lines	Patch %	Lines
src/index.jsx	0.00%	28 Missing ⚠️
src/users/data/api.js	88.88%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #465      +/-   ##
==========================================
+ Coverage   85.94%   90.49%   +4.54%     
==========================================
  Files         185      185              
  Lines        3879     3894      +15     
  Branches      959      966       +7     
==========================================
+ Hits         3334     3524     +190     
+ Misses        527      357     -170     
+ Partials       18       13       -5     

☔ View full report in Codecov by Sentry.
📢 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.

[ankit-sonata]

@psrigummadidala code coverage for this PR is currently around 58%, which falls short of our required threshold of 86%.
Please enhance the test coverage to align with the projects quality standards.

[psrigummadidala]

Hey @Faraz32123 could you please help review/merge this PR

[Faraz32123]

Hey @Faraz32123 could you please help review/merge this PR

Hi @psrigummadidala, can you close this PR and make a PR against edx/frontend-app-support-tools
fork repository.