Refactor TextInput related components tests from Enzyme to React Testing Library

[nataliepina]

Description

This issue is related to refactoring the TextInput.test.tsx, TextInputWithButtons.test.tsx, Textarea.test.tsx and TextInputWithBadges.test.tsx files.

We've recently been migrating our tests from Jest + Enzyme to Jest + testing-library/react to support a full migration to React 18.

You may refer to this previous PR beginning the migration for code examples - #771. Or you can find many code examples throughout other component tests using react testing library within the codebase.

Acceptance Criteria

Refactor the test to use React Testing Library instead of Enzyme (which is no longer supported with React 18).

More information: Migrate from Enzyme

How to Contribute

Please review the contributing documentation beforehand.

Steps to Contribute:

1. Fork the repository.
2. Clone it to your local system.
3. Create a new branch.
4. Make your changes. Make sure that tests are still passing. To update snapshot tests, run npm run test -- -u and include the updated tests in your commit.
5. Commit your changes. When committing prefix your commit message with the appropriate conventional commit type. For example, refactor: <component_name> tests.
6. Push up your changes. In GitHub, click the compare & pull request button to begin drafting your pull request.
7. Fill out the pull request form and attach the "ready for review" label when complete.

[taksuparth]

@nataliepina I can pick this up

[nataliepina]

Sounds good! Thanks for all your help with testing improvements @taksuparth.

[taksuparth]

@nataliepina do let me know if there are more challenging and new items in your planned release which I can pick it up

[nataliepina]

@nataliepina do let me know if there are more challenging and new items in your planned release which I can pick it up

We definitely have some things in the works. We're nearly done with the big migration from class components and enzyme refactoring. There are many more improvements in the pipeline. I'll add some more challenging issues here shortly. Thanks!

[github-actions]

🎉 This issue has been resolved in version 11.2.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀