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

Add fuzz-testing #6102

Open
harshitasao opened this issue Aug 26, 2024 · 7 comments
Open

Add fuzz-testing #6102

harshitasao opened this issue Aug 26, 2024 · 7 comments
Assignees
Labels
feature-request All issues for new features that have not been committed to needs-discussion

Comments

@harshitasao
Copy link

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.

@harshitasao harshitasao added feature-request All issues for new features that have not been committed to needs-discussion labels Aug 26, 2024
@github-staff github-staff deleted a comment from Lxx-c Oct 23, 2024
@github-staff github-staff deleted a comment from Lxx-c Oct 23, 2024
@JorTurFer
Copy link
Member

Ping @kedacore/keda-core-contributors

@zroubalik
Copy link
Member

I like this

@wozniakjan
Copy link
Member

it can help find subtle bugs not covered by our unit / e2e tests. Sounds good to me.

@zroubalik
Copy link
Member

@harshitasao shall I assign this to you? Are you willing to contribute this?

Copy link

stale bot commented Feb 2, 2025

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.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Feb 2, 2025
Copy link

stale bot commented Feb 9, 2025

This issue has been automatically closed due to inactivity.

@stale stale bot closed this as completed Feb 9, 2025
@github-project-automation github-project-automation bot moved this from To Triage to Ready To Ship in Roadmap - KEDA Core Feb 9, 2025
@harshitasao
Copy link
Author

harshitasao commented Feb 10, 2025

@harshitasao shall I assign this to you? Are you willing to contribute this?

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?
Thank you.

@zroubalik zroubalik reopened this Feb 10, 2025
@github-project-automation github-project-automation bot moved this from Ready To Ship to Proposed in Roadmap - KEDA Core Feb 10, 2025
@stale stale bot removed the stale All issues that are marked as stale due to inactivity label Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request All issues for new features that have not been committed to needs-discussion
Projects
Status: Proposed
Development

No branches or pull requests

6 participants
@zroubalik @wozniakjan @JorTurFer @harshitasao and others