Fuzz Testing on GitHub Actions


I’ve been working on converting some CI workflows to the new GitHub actions beta and I had a question about what I’m allowed to execute on the public action runners.

Currently I’m running AFL (a fuzzing program) on my parsers during CI for a duration of 5 minutes to catch any fatal crashes that might otherwise be missed in a code review or handcrafted unit tests. In addition to that, I run some benchmarks and archive the results (with the intention of catching major regressions. I recognize that performance testing on public runners might not be reliable).

Does this fall under usage of GitHub actions for CI/CD of my GitHub hosted project?


1 Like

That is a great use case for Actions! In general, you should feel free to explore creative uses of Actions, short of any abuse scenarios like crypto mining or spam. Our abuse policy is laid out here.