-
Notifications
You must be signed in to change notification settings - Fork 1.1k
add tests for releasesync #1089
add tests for releasesync #1089
Conversation
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.
LGTM. I admit I have not tried to fully understand the code as it stands. But some test coverage is very welcome!
// and returns them organised by namespace and chart release name. | ||
// map[namespace] = []releaseFhr. | ||
func (rs *ReleaseChangeSync) getCustomResources( | ||
ifClient ifclientset.Clientset, |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
You'll need to rebase on master and rerun You may as well squash a couple of the fixup commits while you're there ;-) |
Ok, will rebase/dep/squash as you say. I had a couple of questions (re potential bugs) about the code in my PR; should I open separate issues for them, or ask on slack? |
Probably not; I think it's reasonable to leave a FIXME comment there and move on for now.
Yes that is odd. Forensics (git blame) indicates that it was part of a fairly large set of changes regarding how git repos were used. Given that, and the alpha status of the helm operator, it's plausible that this particular code is logically wrong but (mostly) works. I reckon this one is worth an issue. |
843f9b9
to
32b2a21
Compare
Ok, added the fixme comment. I did the squash/etc, but please have another look because I'm pretty new to multi-user git workflows and it's possible I messed something up. I'll open an issue for the late pull. |
#1092 for the odd pull timing. |
Brill 🌟 thanks @ncabatoff |
Here are some tests for releasesync to address #1037. Beyond the additional tests, I:
Questions:
I'd be happy to continue down this path and add more tests if my approach is satisfactory to the maintainers, though I think sync() is the only other method in this package that's particularly wanting testing.