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

Add support for non-string fields in custom .status wait condition #8

Open
yorugac opened this issue Sep 17, 2024 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@yorugac
Copy link
Collaborator

yorugac commented Sep 17, 2024

Currently, it's possible to wait for a custom .status field so long as it's a string, e.g.:

env.wait({
    kind: "TestRun",
    name: "k6-sample",
    namespace: "fancy-testing",
    status_key: "stage",
    status_value: "finished",
  }, {
    timeout: "2m",
    interval: "1s",
  });

Here, .status.stage is a string.

Support for at least numbers might also be beneficial in some testing scenarios. For example, there are common integers in status like .status.active or status.succeeded in Kubernetes Jobs.

One possible way to define would be something like this:

env.wait({
    kind: "Job",
    name: "my-job",
    status_key: "succeeded",
    status_gt: 0, // gt = greater than
  }, {
    timeout: "2m",
    interval: "1s",
  });
@yorugac yorugac added the enhancement New feature or request label Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant