Chore: Updated tests for step 62

[maxstrater]

Checklist:

• [ x] I have read and followed the contribution guidelines.
• [x ] I have read and followed the how to open a pull request guide.
• [x ] My pull request targets the main branch of freeCodeCamp.
• [ x] I have tested these changes either locally on my machine, or GitPod.

Closes #54502

[camperbot]

Thanks for your pull request.

Please remove the changes made to the non-English versions of the files. No need to close this pull request; just add more commits as needed.

We require you to change only English versions of files in the codebase. Translations to corresponding files in other world languages are managed on our translation platform. Once your pull request is merged, changes will be synced automatically to other world languages.

Please visit our contributing guidelines to learn more about translating freeCodeCamp's resources.

As always, we value all of your contributions.

Happy contributing!

---

Note: This message was automatically generated by a bot. If you feel this message is in error or would like help resolving it, feel free to reach us in our contributor chat.

[camperbot]

Hello,

Firstly, thank you for submitting this pull request!

As you navigate through the process, we have a PR checklist to ensure consistency and quality in our contributions. We kindly ask that you genuinely follow through with each point. This not only facilitates the review process but also demonstrates a mutual respect for the community's efforts.

If you're unfamiliar with certain aspects, our contributing guidelines are a helpful resource to get you up to speed.

**Friendly Pointers (click to expand)**

1. Editing on GitHub: While it's possible to edit files directly on GitHub, it's typically better not to. This helps avoid inadvertent mistakes like typos that can disrupt tests.

2. Pull Request Title: Please ensure the PR title follows our convention.

3. Linking Issues: Please ensure you link issues using the designated method. Simply update the XXXXXX in the PR description to include the issue number. This keeps our records organized and clear.

4. Engaging with the Team: We know you're eager, but kindly keep mentions and review requests limited. Our maintainers are always on the lookout and will attend to PRs in the order they come in.

5. Branch Management: It's a good practice not to work directly off your main branch. Creating separate branches for different changes allows you to smoothly update your PR even as the main repository progresses.

Please note, there's no need to close this PR. If you have questions or need guidance refining your contribution, don't hesitate to ask. Our community is here to assist.

Thank you for your enthusiasm in contributing to our project. We eagerly await more contributions from you!

Happy Contributing! 🌟