Coverage-guided fuzz testing - Java & javafuzz engine

Problem to solve

Our existing JQF fuzz engine struggles with certain use cases, such as Java Spring.

Intended users

User experience goal

Fuzz engine choice should be transparent to user aside from a variable to let them to choose the one they want.

Proposal

Add support for javafuzz as the underlying fuzz engine.

Ensure Java Spring framework works successfully.

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.