-
Notifications
You must be signed in to change notification settings - Fork 33
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
Does it support permutations on optional query parameters? #19
Comments
to be honest, it only seems to make test permutations for request body, which is not really helpful for path parameters and query params based endpoints? |
I have an endpoint with aprox 40 optional query parameters. The simplest way to add tests for these query params is to make 40 additional tests dynamically for the 40 query parameters. Since we have query param validation, any invalid query param will fail. Thus ensuring that all documented query params is allowed and returns 200 OK (and also work with the provided examples) |
I see now that the code is using query params if they are required. So I would guess it should be quite possible to "fix" this issue of mine :) |
at least make one test with all optional query params and another with no optional query params. What do you think @allenheltondev ? |
dang .. you say right here that its designed to only mutate required request body params
Well well I hope both the implementation and the readme can be updated to support optional or default mutation of optional query params too. Path params is not optional so its only about query params. |
I have a basic example working perfectly, but the problem is that this "basic example" is an endpoint with a lot of optional query parameters. Therefore I see test output like this:
which is ok I guess, to just test that the endpoint works in general. but it does not test permutations on query params...
Is that something omitted on purpose @allenheltondev ? If needed I could probably whip something up if I get some pointers
The text was updated successfully, but these errors were encountered: