Extend the list of tests for Fuzzer

[o-kopysov]

We need to increase the coverage of fuzzer tests.
First, we have to add tests for methods that have string/int inputs (such tests can be easily implemented).
After that, we have to try to cover controller endpoints.

[yashpandey06]

Hey @o-kopysov , this issue seems like interesting , should i work on this

LPVSPayloadUtil file needs a lot of test-coverage.

[o-kopysov]

@yashpandey06 The current fuzzer is not functioning correctly. For more information, please refer to this issue: #405. We are awaiting a resolution before proceeding with any related tasks.

[o-kopysov]

Hello @yashpandey06 . The basic fuzzing workflow has been fixed in #613. Therefore, if you are interested in adding new fuzzing tests, you are highly encouraged to contribute to the LPVS project!

[yashpandey06]

@o-kopysov thanks for the information .

[ting-hong-shieh]

I’d like to take this. I’ll start with fuzz coverage for public methods that accept string or integer inputs, using the workflow fixed in #613. I’ll inventory the covered methods in the PR, then cover controller endpoints that fit the existing Jazzer harness and document any endpoint-specific blocker with a reproducible result.