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

ci(fuzz tests): graphql fuzz testing #3760

Draft
wants to merge 72 commits into
base: main
Choose a base branch
from

Conversation

iainsproat
Copy link
Contributor

Description & motivation

⚠️ Draft, do not merge yet.

This adds fuzz testing of the graphql API.

Changes:

  • GitHub Action workflow to fuzz test the speckle server graphql API

To-do before merge:

Screenshots:

Validation of changes:

Checklist:

  • My pull request follows the guidelines in the Contributing guide?
  • My pull request does not duplicate any other open Pull Requests for the same update/change?
  • My commits are related to the pull request and do not amend unrelated code or documentation.
  • My code follows a similar style to existing code.
  • I have added appropriate tests.
  • I have updated or added relevant documentation.

References

Copy link

linear bot commented Jan 3, 2025

@gjedlicska
Copy link
Contributor

What is our goal with this?

@iainsproat
Copy link
Contributor Author

What is our goal with this?

It was a personal festive season project.

Partially it's about discovering incorrect status codes (especially 5XX) or graphql errors we're returning in API responses. And partially about discovering actually-exploitable security vulnerabilities, if any.

It discovered 9 potential issues in the short 3 minutes test it ran. (And the equivalent REST API fuzzer caught a couple of issues I've fixed already.)

If it's useful, it could run weekly against HEAD of main branch rather than being a check (and delay/blocker) on PRs.

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

Successfully merging this pull request may close these issues.

2 participants