-
Notifications
You must be signed in to change notification settings - Fork 11
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
fix: Support default CR starting with dashes #149
fix: Support default CR starting with dashes #149
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.
Consider it approved with suggestion :) The change looks good, one suggestion would be if we could consider streamlining the test cases (only if time allows and you feel like doing it)...
It looks as if we have a set of very similar tests where each is having a shared core (the minimal information that is put into the module template) and each test adding a small part on top (e.g., when associated resources are present, when downtime is set, ...) Would it be possible to use the pattern with an array of test cases where we pass assert functions to the test case? We could have one assert function that is used by all tests verifying the common part, and then pass one function that verifies the specific addition by this test. This would make it easier to see the common part, the individual changes by each test, and make it more robust if things change in the common part in the future.
c5b3ffd
to
43fbb82
Compare
74f16de
to
e9a0899
Compare
e9a0899
to
d0d0098
Compare
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.
Nice!
Description
Changes proposed in this pull request:
Related issue(s)
Resolves #143