Add collectors to Lifecycle Operator Integration Tests

[RealAnna]

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:

• collect logs of lifecycle-operator
• collect logs of metrics-operator
• run a kubectl describe for Workload Version, App Version
• if it exist also kubectl describe of the job (task)

examples can be found here

DoD

• [ ] manually verify that when the test fails, the logs and describes are visible in the shell

[UtkarshUmre]

@RealAnna please assign this issue to me

[github-actions[bot]]

This issue will be unassigned in 1 week if no further activity is seen. If you are active please provide an update on the status of the issue and if you would like to continue working on it.

[UtkarshUmre]

hey @RealAnna could you please share the link to the lifecycle operator integration test again? The current link is leading to a 404 error

[RealAnna]

@UtkarshUmre the new link is updated thank you for the catch :)

[RealAnna]

@UtkarshUmre we updated the ticket for the chainsaw test suite if you are interested in picking this up again... The solution is very similar, but we want to avoid adding kuttl test since we have a pr ready to remove them...

[eddycharly]

@RealAnna it is now possible to register catch blocks at the test level or even at the config level