Skip to content
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

Possibility to set the next request #184

Open
scheroiu opened this issue Dec 4, 2023 · 1 comment
Open

Possibility to set the next request #184

scheroiu opened this issue Dec 4, 2023 · 1 comment
Labels
enhancement New feature or request status:planned We plan to work on this

Comments

@scheroiu
Copy link

scheroiu commented Dec 4, 2023

We are running into the issue that when I want to retrieve data from a gRPC service the data is not yet available (in the background a job is running). Using a timeout is unreliable.

The possibility to "Loop over a request" or "set Next Request" would somehow solve the problem. Similiar to postman.setNextRequest() https://learning.postman.com/docs/collections/running-collections/building-workflows/

The flow in the test is as follows:

  • We start a job from a gRPC request.
  • We check that the job has started
  • we wait for X seconds (this is the problematic part)
  • We retrieve the data from the service (this is unreliable as sometimes the data is not there, because the job didn't finish)
@scheroiu scheroiu added the enhancement New feature or request label Dec 4, 2023
@CommonGuy
Copy link
Contributor

Thank you for your feature request, we added this to our roadmap.

Maybe the following workaround could work for you?

  1. Create an new operation that checks whether the data is there (in a test via Scripting)
  2. Create a script that continously invokes that operation via the Kreya CLI until the test passes
  3. After that test passes, invoke the operation with the "real test script" that requires said data

@CommonGuy CommonGuy added the status:planned We plan to work on this label Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request status:planned We plan to work on this
Projects
None yet
Development

No branches or pull requests

2 participants