-
Notifications
You must be signed in to change notification settings - Fork 224
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
Changes to xSQLServerLogin (Fixes #105, #31) #106
Conversation
Hi @johlju, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution! The agreement was validated by Microsoft and real humans are currently evaluating your PR. TTYL, MSBOT; |
Reviewed 3 of 5 files at r1, 1 of 2 files at r2. Tests/Unit/MSFT_xSQLServerLogin.Tests.ps1, line 179 [r2] (raw file):
change this to 'user does not exist' Comments from Reviewable |
Thank you so much for adding in all these tests! |
fd1d4d9
to
0620a28
Compare
@mbreakey3 It's fun coding these test, I learn a lot! 😄 |
Reviewed 2 of 2 files at r3. Tests/Unit/MSFT_xSQLServerLogin.Tests.ps1, line 120 [r3] (raw file):
should this be 'Should return the state as present'? Tests/Unit/MSFT_xSQLServerLogin.Tests.ps1, line 144 [r3] (raw file):
Again, should this be 'Should return...'? Tests/Unit/MSFT_xSQLServerLogin.Tests.ps1, line 198 [r3] (raw file):
You shouldn't be calling this function more than once in an It statement - divide it up into multiple It statements Tests/Unit/MSFT_xSQLServerLogin.Tests.ps1, line 227 [r3] (raw file):
'group exists' Tests/Unit/MSFT_xSQLServerLogin.Tests.ps1, line 240 [r3] (raw file):
should this be 'Should return the desired state as $true..' ? Tests/Unit/MSFT_xSQLServerLogin.Tests.ps1, line 345 [r3] (raw file):
rephrase this It statement Tests/Unit/MSFT_xSQLServerLogin.Tests.ps1, line 428 [r3] (raw file):
rephrase this 'It' statement Comments from Reviewable |
Reviewed 1 of 5 files at r1, 1 of 2 files at r3, 3 of 3 files at r4. Tests/Unit/MSFT_xSQLServerLogin.Tests.ps1, line 179 [r2] (raw file):
|
@mbreakey3 Did I break AppVeyor with this commit? How can I see what's wrong? |
69a1059
to
8ce229e
Compare
@mbreakey3 Never mind, I missed that you merged in a PR. I resolved the conflict and now AppVeyor is happy again 😄 |
Reviewed 2 of 3 files at r4, 1 of 1 files at r5. DSCResources/MSFT_xSQLServerLogin/MSFT_xSQLServerLogin.psm1, line 154 [r5] (raw file):
you don't need to add the space within the brackets and parentheses. But there should be one after the 'if' before the '(' on the line below DSCResources/MSFT_xSQLServerLogin/MSFT_xSQLServerLogin.psm1, line 235 [r5] (raw file):
Again, the spaces aren't needed within the parentheses, but there should be a space after the 'if' Comments from Reviewable |
Reviewed 1 of 1 files at r5, 1 of 1 files at r6. DSCResources/MSFT_xSQLServerLogin/MSFT_xSQLServerLogin.psm1, line 154 [r5] (raw file):
|
5ed732e
to
1a66fe3
Compare
Reviewed 1 of 1 files at r6, 2 of 2 files at r7. Comments from Reviewable |
Now there's just the merge conflicts.... |
Also cleaned up the code somewhat
Fixed so the Set-method throws correctly. Fixed Login class so it can be called from the test correctly when using an [Object] instead of [Server] class.
Added a function when dropping a login so tests can mock the function
Tests generated false positives due to code errors in the resource. Fixed that as well.
Fixed typos
Fixed style comments from review Added SupportsShouldProcess and ShouldProcess to Set-method
The description of the parameters for xSQLServerLogin was not aligned with the schema.
1a66fe3
to
39cb1a4
Compare
@mbreakey3 Resolved the conflicts |
Comments from Reviewable |
This change is