lifecycle-toolkit
lifecycle-toolkit copied to clipboard
Introduce tests for lifecycle-operator bugs
Recently multiple small bugs were found and fixed as part of this PR.
The places are:
- https://github.com/keptn/lifecycle-toolkit/pull/3113/files#diff-7e3a3dd6a5940394c614f51b5abf528919d2593178aad9cfbbe963bdc261dc6bR212
- https://github.com/keptn/lifecycle-toolkit/pull/3113/files#diff-7e3a3dd6a5940394c614f51b5abf528919d2593178aad9cfbbe963bdc261dc6bR238
- https://github.com/keptn/lifecycle-toolkit/pull/3113/files#diff-9a3cc86b3f6c7660bf48ab0906ad69cc9500e27fc6b648f0d577f92f0078933dR162
Introduce unit tests to cover the affected functionality
Hi @odubajDT , I can try to solve this issue. Can you assign it to me?
Thank you!
Hi @SohamRatnaparkhi are you actively working on this issue? Since you have this issue assigned for aprox. 10 days, we usually unassign asignees from their issues if there is no activity to not block other potential contributors from starting to tackle them.
Thanks for the update!
Hey @odubajDT Really sorry for holding on to the issue. I'm busy right now and can't solve it. Feel free to assign it to someone else.
Once again, I'm really sorry :)
No worries, thank you very much for your answer! :) If you have time in the future, we would be happy if you reach out to us for potentially another issue!
Hey I can take on this one If no one is working
Hi @Bharadwajshivam28 are you actively working on this issue? Since you have this issue assigned for aprox. 3 weeks, we usually unassign asignees from their issues if there is no activity to not block other potential contributors from starting to tackle them.
Thanks for the update!
Due to inactivity, unassigning @Bharadwajshivam28 from this issue. Feel free to request a different issue!
Hi @odubajDT I would like to work on the above issue
@YashPimple I assigned it to you but please before you start, there is a small change required in the PR you have opened https://github.com/keptn/lifecycle-toolkit/pull/3143. try to please finish this one first before you start with a new one
Hi! @odubajDT, I would like to take up this issue.
Since the non-blocking mode does not introduce any errors in the controller, we can write a unit test with a mock handler that does not return any errors when the KeptnAppVersionStatus resembles the manifest in the docs
Am I correctly understanding the task here?
@Jay179-sudo sure thing, I assigned it to you