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

Integrate fuzz tests in source tree and extend test cases #209

Open
bshastry opened this issue Jun 24, 2018 · 5 comments
Open

Integrate fuzz tests in source tree and extend test cases #209

bshastry opened this issue Jun 24, 2018 · 5 comments
Labels

Comments

@bshastry
Copy link

Hi,

In the long run, it is better to merge fuzz tests in your source tree instead of in oss-fuzz repo.

Also, it would be useful to extend the current test set with more test cases for other parsing APIs perhaps.

I'd be happy to take this up together with the dev team :-)

@obgm
Copy link
Owner

obgm commented Jun 26, 2018

Thank you, any help with that is highly appreciated! What exactly needs to be added to the source tree to do that?

And yes, more tests would be good. As far as I understand, specific corpora could enhance the testing as well.

@obgm obgm added the testing label Jun 26, 2018
@bshastry
Copy link
Author

Thank you, any help with that is highly appreciated! What exactly needs to be added to the source tree to do that?

Basically, all the fuzzer test cases need to move to this repo in a folder like tests/oss-fuzz from oss-fuzz. This will help you maintain fuzzer test cases like you maintain other code.

And yes, more tests would be good. As far as I understand, specific corpora could enhance the testing as well.

Exactly. There are two things that could be added:

  • corpora (generated by the fuzzer), dictionaries specific to test cases
  • new test cases for APIs that process potentially attacker controlled data

@bshastry
Copy link
Author

bshastry commented Jul 2, 2018

Hello,

Any updates on this? 😄 (CC #211)

@bshastry
Copy link
Author

Ping :-)

@obgm
Copy link
Owner

obgm commented Jan 9, 2020

I have not yet have a deeper look nor found somebody to contribute to this. Anyway, feel free to open a PR addressing this any time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants