-
Notifications
You must be signed in to change notification settings - Fork 181
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
base: main
Are you sure you want to change the base?
ci(fuzz tests): graphql fuzz testing #3760
Conversation
- override default settings
- update openapi specification for images in response body
- allows rate limiter to be enabled or disabled explicitly - previously implied based on whether NODE_ENV is 'test', which may not be desired behaviour - example .env file for testing now explicitly disables it
…web-511-fuzz-test-speckle-server-rest-api
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. |
Description & motivation
This adds fuzz testing of the graphql API.
Changes:
To-do before merge:
Screenshots:
Validation of changes:
Checklist:
References