W-20911534: adding unit tests for sf-payments-express components

[nayanavishwa]

Description

Types of Changes

• Includes unit tests for sf-payments-express components in template-retail-react-app package.

Coverage:

• test results for app/pages/checkout/partials/sf-payments-sheet.test.js:

• test results for app/utils/sf-payments-utils.test.js‎:

---

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Documentation update
• Breaking change (could cause existing functionality to not work as expected)
• Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

• Removing a public function or component or prop
• Adding a required argument to a function
• Changing the data type of a function parameter or return value
• Adding a new peer dependency to package.json

Changes

• template-retail-react-app/app/components/sf-payments-express/index.test.js
• template-retail-react-app/app/components/sf-payments-express-buttons/index.test.js

How to Test-Drive This PR

• checkout this branch and run npm run test at project directory.

Checklists

General

• Changes are covered by test cases
• CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance

You must check off all items in one of the follow two lists:

• There are no changes to UI

or...

• Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
• Changes comply with WCAG 2.0 guidelines levels A and AA
• Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

• Changes include a UI text update in the Retail React App (which requires translation)

[cc-prodsec]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[rasbhat]

Linting: Please run npm run lint. If you hit any issues, you can usually resolve them quickly with npm run lint:fix

Testing: We aim for at least 70% test coverage. Please attach the coverage report along with the test results.