-
Notifications
You must be signed in to change notification settings - Fork 65
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
xVhdFileDirectory Unit Tests #180
xVhdFileDirectory Unit Tests #180
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #180 +/- ##
===================================
Coverage 83% 83%
===================================
Files 11 11
Lines 1401 1401
===================================
Hits 1166 1166
Misses 235 235 |
@mcollera or @aromano2 you are listed as maintainers for this module. Do you have time to review this one? |
@johlju yes looking at it now, thanks! |
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.
Reviewed 1 of 1 files at r2, 1 of 1 files at r3.
Reviewable status: complete! all files reviewed, all discussions resolved
* xVhdFileDirectory initial unit tests added * xVhdFileDirectory unit tests, added GetFreeDriveLetter * Updated CHANGELOG.md * xVhdFileDirectory unit test style fixes * xVhdFileDirectory fixed unit tests for appveyor * xVhdFileDirectory additional unit tests * xVhdFileDirectory unit tests - tidy-up & Get-FreeDrive fix * xVhdFileDirectory unit tests - fixed 'Describe' block description * Merge branch 'dev' into xVhdFileDirectory_UnitTests
Pull Request (PR) description
PR that adds some basic initial unit tests for the xVhdFileDirectory resource. There is a bug that I'd like to fix around copying to VHDs with multiple partitions - before I look into that, I'd like to put some unit tests in place.
I have not covered off tests for any of the private functions within the resource as of yet, as I may propose to change a couple.
This Pull Request (PR) fixes the following issues
Task list
Entry should say what was changed, and how that affects users (if applicable).
and comment-based help.
This change is