[Nathaniel Brough (nathaniel-brough)]

Description

This PR adds a fuzz testing harness and the necessary build configurations, to get CuraEngine integrated into oss-fuzz. This is in initial integration as a follow up on #1603.

See corresponding draft integration PR here google/oss-fuzz#10155

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

This PR does not add any new functionality instead it adds ONLY fuzz testing harnesses.

• FuzzGcodeExport, fuzzes the gcode export library with randomized inputs.

Test Configuration:

• Operating System:

Checklist:

• My code follows the style guidelines of this project as described in UltiMaker Meta
• I have read the Contribution guide
• I have commented my code, particularly in hard-to-understand areas
• I have uploaded any files required to test this change

[Nathaniel Brough (nathaniel-brough)]

cc Jaime van Kessel (@nallath) as you are listed as primary contact for oss-fuzz configs :)

[Nathaniel Brough (nathaniel-brough)]

Jelle Spijker (@jellespijker) Friendly ping :) I need to work through some of the other conflicts that I've merged incorrectly. Before I do that, is this PR of any interest?

[Jelle Spijker (jellespijker)]

Hi @silvergasp

Apologize for taking this long to reply. My GitHub notification probably got lost in the 600+ notifications if I'm working on GH actions and I get the failed run notification.

At a first glance I would say, yes Fuzz testing is something that we want I will bring this up with the team such that we can plan the review and testing in our sprint

[Nathaniel Brough (nathaniel-brough)]

Not a problem, let me know if you have any further queries regarding this PR/oss-fuzz or just more generally about fuzzing.