-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add fuzz-testing #6102
Comments
Ping @kedacore/keda-core-contributors |
I like this |
it can help find subtle bugs not covered by our unit / e2e tests. Sounds good to me. |
@harshitasao shall I assign this to you? Are you willing to contribute this? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
Hello @zroubalik I apologize for the delayed response. I would like to work on this, so could you please reopen the issue and assign it to me? |
Proposal
Fuzz testing or Fuzzing is a Black Box software testing technique, which basically consists in finding implementation bugs using malformed/semi-malformed data injection in an automated fashion.
Integrate the project with OSS-Fuzz by following the instructions here.
Part of #6085
Use-Case
To increase security of the project.
Is this a feature you are interested in implementing yourself?
Yes
Anything else?
Maintainers help is highly appreciated. For example, helping in identifying the components where fuzz testing will be added.
The text was updated successfully, but these errors were encountered: