-
Notifications
You must be signed in to change notification settings - Fork 122
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 collectors to Lifecycle Operator Integration Tests #2698
Comments
@RealAnna please assign this issue to me |
This issue will be unassigned in 1 week if no further activity is seen. |
hey @RealAnna could you please share the link to the lifecycle operator integration test again? The current link is leading to a 404 error |
@UtkarshUmre the new link is updated thank you for the catch :) |
@UtkarshUmre we updated the ticket for the chainsaw test suite if you are interested in picking this up again... |
@RealAnna it is now possible to register catch blocks at the test level or even at the config level |
This issue will be unassigned in 1 week if no further activity is seen. |
un-assigning, due to inactivity |
Given this generic example on how to add a catch statement to chainsaw tests, we should add them in each lifecycle operator integration test that:
examples can be found here
DoD
The text was updated successfully, but these errors were encountered: