feat(testing): Add comprehensive tests for unicode and special characters

[lalitc375]

This pull request introduces a significant number of new test cases to our test suite. These tests cover a wide range of scenarios involving unicode characters, escape sequences, and other special characters within field paths and values.

Motivation:

The primary motivation for this change is to increase our test coverage and make the codebase more robust. This will be particularly important for future work that may involve switching the underlying JSON serialization and deserialization library to std. Having a comprehensive test suite will enable us to:

• Validate new libraries: We can confidently evaluate and validate new JSON libraries for compatibility with our existing system.
• Prevent regressions: A strong test suite will help us catch any regressions or behavioral changes that might be introduced by a new library.

By strengthening our tests now, we are paving the way for future improvements and ensuring the long-term stability and performance of our code.

[k8s-ci-robot]

Welcome @lalitc375!

It looks like this is your first PR to kubernetes-sigs/structured-merge-diff 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/structured-merge-diff has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @lalitc375. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[lalitc375]

cc: @liggitt @jpbetz

[liggitt]

/ok-to-test

Thanks, looks good at first glance

[liggitt]

/lgtm
/approve

[liggitt]

/lgtm
/assign @jpbetz

[jpbetz]

Excellent. Given how (excessively) accepting we are of field names in CRDs, this makes me feel a lot better about our coverage.

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jpbetz, lalitc375, liggitt

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jpbetz,liggitt]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment