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.

Sign up for GitHub

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

Jump to bottom

Resurrect fuzz testing framework #422

Closed
3 of 4 tasks
ionut-arm opened this issue May 11, 2021 · 1 comment
Closed
3 of 4 tasks

Resurrect fuzz testing framework #422

ionut-arm opened this issue May 11, 2021 · 1 comment
Assignees
@ionut-arm
Labels
code health Issues concerning overall code quality, safety and best practice medium Effort label security Issues related to the security and privacy of the service testing Task related to testing
Milestone
Parsec Release 0.8.0

Comments

@ionut-arm
Copy link
Member

ionut-arm commented May 11, 2021 •
edited
Loading

The current fuzz testing framework has been left behind the Parsec service in terms of development. We need to bring this back up to speed and make sure we can run it (locally).

This issue should only look at the changes needed to allow the fuzzer to run:

  • Make sure all the interface and service types needed have the required traits derived
  • Make sure the corpus is generated correctly for the current incarnation of the wire protocol
  • Add values in the corpus for operations that have been added to the service in the meanwhile
  • Check that all the providers that can we can fuzz test are supported for fuzz testing
@ionut-arm ionut-arm added security Issues related to the security and privacy of the service code health Issues concerning overall code quality, safety and best practice medium Effort label testing Task related to testing labels May 11, 2021
@ionut-arm ionut-arm added this to the Parsec Release 0.8.0 milestone May 11, 2021
@ionut-arm ionut-arm self-assigned this May 11, 2021
@ionut-arm
Copy link
Member Author

The fuzzing framework has been made to build and execute again under #429 . Closing this as the not-covered point (adding new operations and features to the initial corpus) will be done under #437

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ionut-arm ionut-arm

Labels
code health Issues concerning overall code quality, safety and best practice medium Effort label security Issues related to the security and privacy of the service testing Task related to testing
Projects
None yet
Milestone
Parsec Release 0.8.0
Development

No branches or pull requests
1 participant
@ionut-arm