-
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
Improve rose stem coverage #181
Improve rose stem coverage #181
Conversation
631aa3a
to
022688c
Compare
395ac55
to
fe36d88
Compare
fe36d88
to
4876133
Compare
4876133
to
8d137ab
Compare
|
||
ret = {} | ||
for line in output.splitlines(): | ||
if ":" not in line: | ||
continue | ||
key, value = line.split(":", 1) | ||
|
||
if key and value: |
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.
@dpmatthews - This is splitting lines from fcm loc-layout
. Will it ever be false?
Coverage identifies the following remaining holes:
|
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.
Most of this went over my head but good to see coverage up to 94%
…m:wxtim/cylc-rose into 20220913T1539--improve_rose_stem_coverage * '20220913T1539--improve_rose_stem_coverage' of github.com:wxtim/cylc-rose: Update setup.cfg
Some of the methods which act as interfaces to FCM are pretty opaque to me, and there are at least 2 lines where I had to put in considerable effort to ensure that there wasn't a bug. |
Co-authored-by: Ronnie Dutta <[email protected]>
These changes partially address #157
I have added some unit tests designed to cover holes in the functional testing for
rose stem
I translated from Rose 2019.added @dpmatthews as a functional review WRT mocking subprocessed fcm commands.
Requirements check-list
CONTRIBUTING.md
and added my name as a Code Contributor.setup.cfg
.