Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add fuzz-testing #1905

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Conversation

vaibhaavv8
Copy link

@vaibhaavv8 vaibhaavv8 commented Feb 6, 2025

PR Description

This PR introduces a fuzz test for Kruise, specifically targeting the validation of ResourceDistribution resources. The current test focuses on validating the resource field as described in the ResourceDistribution documentation. Over time, this test will be expanded to cover additional aspects and edge cases.

Why do we need this?

Fuzz testing is essential for improving the reliability and security of the Kruise project. By adding this fuzz test, we aim to identify potential bugs, vulnerabilities, or unexpected behavior that may not be caught during standard testing.

Todos

  • Create a proof of concept (POC) for fuzz testing.
  • Add documentation explaining how fuzz testing works within Kruise.
  • Integrate OSS-Fuzz with Kruise for continuous fuzz testing.
  • Explore and add additional fuzz tests to cover more scenarios.
  • Continuously improve and expand fuzz tests as new edge cases emerge.

Additional Notes

This is an ongoing process, and more tests will be added over time to ensure Kruise's robustness.

// @furykerry @hantmac

Signed-off-by: Vaibhav K <[email protected]>
@kruise-bot
Copy link

@vaibhaavv8: PR needs rebase.

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants