-
Notifications
You must be signed in to change notification settings - Fork 26
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
GRPC - cannot simulate gRPC error status, false positive mock response #188
Comments
Hi @szokebarnabas,
Could you please elaborate with an example, what kind of request matchers are you referring to? |
I'm unsure if this is a bug or if this isn't documented or supported. Take HTTP: Camouflage mocks HTTP by having you provide the entire HTTP response in your Similarly in gRPC we have status codes and I may want to do the same thing where I configure camouflage to return GRPC 16 "Unauthorized" so that I can verify my app behaves accordingly when such a thing happens. I don't see it documented. Since I'm proxying with envoy to camouflage, I also would like to set headers but I know I may be asking for too much there. |
* fix: lazy loading the validation modules testinggospels#203 (testinggospels#206) * feat: state helper (testinggospels#207) * feat: cookie support for the capture helper (testinggospels#209) * implement basic error response and metadata. testinggospels#188 * docs: grpc documentation * fix: race condition with lazy loading of the validation adapters (testinggospels#210)
Describe the bug
Hi, apologies in advance if the answer to my question is trivial but I don't have any experience with gRpc and protobufs.
What I would like to achieve is:
To Reproduce
Steps to reproduce the behavior:
mocks:
protos:
Response:
Expected behavior
It's should be possible to define request matchers and return responses accordingly.
Thanks,
Barnabas
The text was updated successfully, but these errors were encountered: