Add test to track config file changes - #1683
Conversation
992e81d to
6733785
Compare
6733785 to
698940e
Compare
698940e to
7c4319d
Compare
7c4319d to
4ec7f69
Compare
4ec7f69 to
5916ef4
Compare
5916ef4 to
f7a5734
Compare
leseb
left a comment
There was a problem hiding this comment.
This looks all good to me. However, I'm wondering if tests/testdata/default_config.yaml should be located elsewhere to gain more visibility. If so, how about renaming it to sample.ilab.config.yaml or sample.config.yaml to indicate that it's a sample configuration file? And have it at the root? or in src? Thanks!
|
Pending from offline discussion, we need to make it clearer that when the test fails users have to run |
f7a5734 to
9a8302b
Compare
9a8302b to
7e949c7
Compare
Discussed offline, we don't want to mix test_data with this proposal, so we will do separately. |
|
@Mergifyio rebase |
✅ Branch has been successfully rebased |
7e949c7 to
78617f8
Compare
|
CI is failing as expected :), I rebased on top of the version flag addition. |
A new test compares the config from `get_default_config` against a default config file in VCS. This allows us to track any change in the git history. Signed-off-by: Christian Heimes <cheimes@redhat.com>
78617f8 to
2d3d670
Compare
A new test compares the config from
get_default_configagainst a default config file in VCS. This allows us to track any change in the git history.See: #1725
Checklist:
conventional commits.