-
Notifications
You must be signed in to change notification settings - Fork 5
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
ENH: add search_by_expression workflow #263
Conversation
this workflow action allows querying generic openstack resources for numerical properties based on an expression - e.g "less-than" or "greater-than" a given threshold Future stackstorm actions will make use of it
375618f
to
a74bbcb
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #263 +/- ##
==========================================
- Coverage 98.20% 98.08% -0.13%
==========================================
Files 195 208 +13
Lines 7636 7989 +353
Branches 460 484 +24
==========================================
+ Hits 7499 7836 +337
- Misses 110 125 +15
- Partials 27 28 +1 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It all looks good for me apart from the possible minor clouds.yaml
typo
@pytest.mark.parametrize( | ||
"output_type", ["to_html", "to_string", "to_objects", "to_props"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just for understanding. This code allows testing of each of the types listed separately if I understand correctly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
parametrize splits the test into 4 parts. Each test uses a different output_type
parameter - set here to_html
, to_string
etc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's to save from writing each test separately - https://docs.pytest.org/en/7.1.x/example/parametrize.html
cloud.ymal -> cloud.yaml Co-authored-by: Nalin Gupta <[email protected]>
this workflow action allows querying generic openstack resources for numerical properties based on an expression - e.g "less-than" or "greater-than" a given threshold
Future stackstorm actions will make use of it