Skip to content
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

Count test coverage more accurately #426

Merged
merged 4 commits into from
Jun 1, 2016
Merged

Count test coverage more accurately #426

merged 4 commits into from
Jun 1, 2016

Conversation

mvidner
Copy link
Member

@mvidner mvidner commented Jan 21, 2016

and also fix an API bug in the process; need to verify that the fix is harmless

Coverage goes down from 56% to 45%, yay!

The run method is normally needed, but the test just pays attention to
the event_loop defined in the mixin.
@jreidinger
Copy link
Member

LGTM, just make rubocop happy: https://travis-ci.org/yast/yast-yast2/builds/103880372#L563

Bootloader::ProposalClient, the only subclass so far, did not need it
because only some kinds of proposals ever call write.
@jreidinger
Copy link
Member

LGTM


def write
# doing nothing is OK. or is it? clarify the API, the docs, actual usage!
end
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I worry it is not OK. If you really call it with write, then you expect it do something.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so possible to overlook bugs. Actual usage is without write, only in very specific modules like used to be network or cio proposal use it as it keep value, so finish client call proposal client with write.

@mvidner mvidner merged commit e09c567 into master Jun 1, 2016
@mvidner mvidner deleted the dont-cover-tests branch July 29, 2016 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants