Add a fuzz test

[kehoecj]

Write a fuzz test for one of the validator types. You can see an example here that I previously worked on. You can take that and modify it or write your own. This will help improve our OpenSSF scorecard score.

[nadsella]

@kehoecj I'm happy to take this on :)

[kehoecj]

Thank you @nadsella ! I assigned this issue to you

[anya004]

Hey @kehoecj, if this is still relevant, please assign to me

[kehoecj]

Hey @kehoecj, if this is still relevant, please assign to me

@anya004 yep, go for it! Let me know if you have any questions

[anya004]

Hi! After reviewing the previous code, I wanted to clarify a few things:

• Was the original code not merged solely due to failing lint checks?
• Would you like me to extend the edge cases for the current implementation?
• Should I focus on a different file type validator instead?
• Finally, would you like me to include updates to the GitHub workflow in the same PR?

Let me know your preferences—thanks!

[kehoecj]

Hi! After reviewing the previous code, I wanted to clarify a few things:

* Was the original code not merged solely due to failing lint checks?

* Would you like me to extend the edge cases for the current implementation?

* Should I focus on a different file type validator instead?

* Finally, would you like me to include updates to the GitHub workflow in the same PR?

Let me know your preferences—thanks!

@anya004

• Yes, the lint checks and work required to get it to run automatically as part of the workflow
• You can definitely extend it or pick a different validator type. You could also probably do something like in the validator unit tests where a single fuzz test scans multiple validator types. Up to you!
• That'd be great if you could but not required

[skirtan1]

Hi @anya004,

Are you working on this? and can we work together on this? I would like to contribute to this issue as well, I took the liberty to open a draft pr: https://github.com/Boeing/config-file-validator/pull/248