Skip to content

(MODULES-10384) - Registry value check tightened #343

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

Merged
merged 1 commit into from
Jan 21, 2020

Conversation

david22swan
Copy link
Member

@david22swan david22swan commented Jan 21, 2020

No description provided.

@david22swan david22swan requested a review from a team as a code owner January 21, 2020 09:42
@david22swan
Copy link
Member Author

Screen Shot 2020-01-21 at 9 28 32 AM

@codecov-io
Copy link

codecov-io commented Jan 21, 2020

Codecov Report

Merging #343 into master will not change coverage.
The diff coverage is 0%.

Impacted file tree graph

@@          Coverage Diff           @@
##           master    #343   +/-   ##
======================================
  Coverage    56.2%   56.2%           
======================================
  Files          20      20           
  Lines         758     758           
======================================
  Hits          426     426           
  Misses        332     332
Impacted Files Coverage Δ
lib/puppet_x/sqlserver/features.rb 30.68% <0%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d371737...d3fd861. Read the comment docs.

@sanfrancrisko
Copy link
Contributor

I can't see any unit tests for this method or any other methods that calls it in the module, so I guess the question comes down to whether we want to add one?

Given it's essentially just reporting the values from the registry, I'm not sure I'd see much additional benefit, however I am a big proponent of adding tests for scenarios that caused bugs. Might be worth looking at how much time it would take to write a test for get_instance_info or get_instance_features? If it's going to take a lot of mocking / stubbing, then probably not worth it.

Code change LGTM

@david22swan
Copy link
Member Author

david22swan commented Jan 21, 2020

I can't see any unit tests for this method or any other methods that calls it in the module, so I guess the question comes down to whether we want to add one?

Given it's essentially just reporting the values from the registry, I'm not sure I'd see much additional benefit, however I am a big proponent of adding tests for scenarios that caused bugs. Might be worth looking at how much time it would take to write a test for get_instance_info or get_instance_features? If it's going to take a lot of mocking / stubbing, then probably not worth it.

Code change LGTM

@cmccrisken-puppet Talked to Schmidt and come to the decision that no test is needed right now.

@sanfrancrisko sanfrancrisko merged commit 697b6cc into puppetlabs:master Jan 21, 2020
@david22swan david22swan deleted the MODULES-10384 branch January 21, 2020 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants