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

Issue/23081/report property event for insync exceptions #2036

Conversation

kylog
Copy link

@kylog kylog commented Nov 6, 2013

No description provided.

zaphod42 and others added 5 commits November 5, 2013 15:31
This makes non-public methods explicitly private. It also reorders the
methods to read in a manner where the top is the public and highest
level, and it becomes more low level as we move down the file.
This changes removes a large block of unit tests, comprising
1296 individual tests built up via 8 nested 'each' loops. Why
remove so many tests?

First, in the course of refactoring for #23081 we triggered
test failures in this block only when we also triggered a test
failure elsewhere, and conversely, it didn't trigger failures
where other individual tests did register a useful failure.

Second, several people have stared at this unit test block
and not been able to figure out what it is uniquely testing.

So in short the value of this test block is not clear, so we're
removing it.  Of course, if we hit future gaps in unit test coverage,
we'll add tests back in to cover gaps.
zaphod42 added a commit that referenced this pull request Nov 6, 2013
…-for-insync-exceptions

Issue/23081/report property event for insync exceptions
@zaphod42 zaphod42 merged commit 72f1eeb into puppetlabs:master Nov 6, 2013
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.

None yet

2 participants