Replies: 2 comments
-
Hello hello, thanks for the feedback
Yes, I have highlighted it in the documentation
You can capture data from previous steps and use it in consequent steps (in documentation)
You should create a separate token for CI/CD that does not expire
Realtime APIs are on backlog, but I still need to think how it will be implemented
I don't think makes much sense. Typically gRPC-Web Gateway is just a proxy to the gRPC API?
Client and server streaming is already supported by cool-grpc, but not Bidirectional Streaming and not for gRPC-Web
You can capture data from a previous step and send it in the metadata field in the next step
Should be fixed now. Can you try again?
Yes, you should be able to. Imports are not supported though
Yes, I have highlighted it in the documentation
https://docs.stepci.com/reference/workflow-syntax.html#tests-test-testdata Will take all your feature and documentations suggestions into consideration I have another question about the gRPC library you use in ezy. I can see us using it as well. Would you be able to publish it as a package on NPM and include documentation how to use it? We can wrap it in our cool-grpc repository for easier access Thank you! |
Beta Was this translation helpful? Give feedback.
-
Hi!
Ah, I thought that it useful when the user wants to create integration test. I don't know is the CI/CD token without expiration is a best practice. Recurrent query by condition I think could be a great feature.
This is not just a proxy, it transmits serialised data by protobuf definitions and deserialise data on income. Also it forms HTTP paths for this proxy.
Yep I will try and return back
For gRPC imports are necessary. In real projects usually protos are divided by files
I think yes, but I need some time. I want to rewrite it and add full test coverage. |
Beta Was this translation helpful? Give feedback.
-
Concepts
https://docs.stepci.com/guides/concepts.html
HTTP APIs
https://docs.stepci.com/guides/testing-http.html
GraphQL APIs
https://docs.stepci.com/guides/testing-graphql.html
gRPC APIs
https://docs.stepci.com/guides/testing-grpc.html
Disclaimer - maybe for all of this features you can use my core library - https://github.com/getezy/ezy/tree/master/src/core
Example of complex case:
Bidirectional streaming → Init request → Send message from client 2 times → Wait for response from server and check data -> Repeat 4 times -> Stop client stream -> Wait for ending server stream. We can discuss about all cases later.
With this test suite:
Getting an error:
12 UNIMPLEMENTED: The server does not implement the method /simple_package.v1/Unary
I think there is a bug in splitting service name, I just want to say that in gRPC we often use tags like
.v1
in package name for version history.Tried to use package without
.v1
:Test suite:
Getting an error:
12 UNIMPLEMENTED: The server does not implement the method /simple_package.SimpleService/Unary
Tried to use it without package by removing
package
definition from proto file.Test suite:
Getting an error:
12 UNIMPLEMENTED: The server does not implement the method /SimpleService.undefined/Unary
You have
main.proto
file with this definition:And your
types.proto
file:If we define
main.proto
in test suite, shall it work and use imported message fromtypes.proto
?Load Testing
https://docs.stepci.com/guides/load-testing.html
Test Data
https://docs.stepci.com/guides/using-test-data.html
Features
Documentation
Reference → Workflow Syntax
Testing HTTP APIs
Testing gRPC APIs
Beta Was this translation helpful? Give feedback.
All reactions