Contributions
Re: How encoding/Decoding of Grpc proto parameters processed in ReadAPI during .proto file import
When sending request from readyapi to some server using grpc. Are some bytes getting padded in the json request or its re-ordered? How this encoding is happening in readyapi while sending request? Kindly let me know your thoughts on this. Thanks, Guru3 years agoPlace ReadyAPI QuestionsReadyAPI Questions938Views0likes0CommentsRe: How encoding/Decoding of Grpc proto parameters processed in ReadAPI during .proto file import
Hi Sonya, Thanks for asking. My query was not solved because this is not a json request/response. Still could not understand how readyapi encodes the request data to server when the grpc request created using the unary call imported from .proto file. So tried modifying the default request data in the grpc unary call based on how we implemented in our code. That modification did not helped, it throws "invalid input length" error after modifying. Any suggestions how to proceed further? How this request data is being set when creating grpc request using the imported API definition? Kindly let me know. Thanks, Guru3 years agoPlace ReadyAPI QuestionsReadyAPI Questions978Views0likes0CommentsRe: SmartBear Presentation -- 'gRPC Support via ReadyAPI!'?
Hi Sonya, Thanks for sharing the webinar link for gRPC Support via ReadyAPI. I have filled the form on the following website for watching the webinar,https://smartbear.com/resources/webinars/grpc-and-readyapi/. But that has some other webinar in that link in the name of "Best Practices in API Development: Creating API Testing workflows that work" which is not relevant. Are you also facing the same? I could not find webinar for "ReadyAPI + gRPC: Enhancing Test Quality Across your Microservices Architecture". Please let me know where can I check this.3 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.2KViews0likes1CommentHow encoding/Decoding of Grpc proto parameters processed in ReadAPI during .proto file import
In our project we have requirement to test the grpc protocol using unary operation. Able to import .proto file successfully in readyapi, but when created the test case using the imported file, the original data of the unary request is mistmatched with the actual data of the proto file. For example: Following is the request data we have got after importing the .proto file in readyapi. we are not sure how this encoding/decoding occurs in readyapi. Request Data from readyapi: { "token1" : "c3RyaW5n", "nonce" : "c3RyaW5n" } But in grpc server we have stored the same data as constants and comparing these constants with the readyapi request. Unfortunately the comparison is not matching with our implementation with the readyapi data received. Below is our two scenarios of comparision, but in none of the case its matching. comparision 1: const test_token = "blablabla" token := []byte(test_token) "if bytes.Compare(token, in.GetToken1()) == 0" comparision 2: const test_token = "c3RyaW5n" token := []byte(test_token) "if bytes.Compare(token, in.GetToken1()) == 0"1.1KViews0likes5CommentsHow to ssh/Integrate cygwin for the remote execution of CLI commands on windows with ReadyAPI ?
Have to ssh the CLI commands on a remote windows server. Unlike linux, could not execute cli commands on remote windows server using readyapi, seems there are pre-requisite should be done for executing the commands remotely. Currently I am getting the following error when tried ssh from readyapi to the remote windows server. Kindly help me out to execute cli commands on readyapi for the windows machine HTTP/1.0 400 BAD REQUEST Content-Type: text/html; charset=utf-8 Content-Length: 192 Server: Werkzeug/1.0.1 Python/3.6.8 Date: Mon, 04 Oct 2021 07:33:38 GMT <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <title>400 Bad Request</title> <h1>Bad Request</h1> <p>The browser (or proxy) sent a request that this server could not understand.</p>3 years agoPlace ReadyAPI QuestionsReadyAPI Questions923Views0likes2Comments