Integration test missing for Test-SqlDscIsDatabasePrincipal

[Copilot]

• Analyze the problem statement and understand requirements
• Review existing Test-SqlDscIsDatabasePrincipal command structure and parameters
• Examine similar integration test patterns (Test-SqlDscIsLogin, Test-SqlDscIsRole)
• Create integration test file following SqlServerDsc guidelines
• Implement test scenarios covering all parameter combinations
• Test database users, roles, fixed roles, and application roles
• Add proper error handling and edge case testing
• Add test to azure-pipelines.yml in appropriate group
• Update CHANGELOG.md with new integration test entry
• Validate syntax and run unit tests to ensure no regressions
• Fix file ending with proper blank line
• Update README.md with correct dependency information

Successfully created comprehensive integration test for Test-SqlDscIsDatabasePrincipal command with the following coverage:

• Database users (with ExcludeUsers parameter)
• Database roles (with ExcludeRoles parameter)
• Fixed roles (with ExcludeFixedRoles parameter)
• Application roles (with ExcludeApplicationRoles parameter)
• Error handling for missing databases
• Pipeline parameter support
• Case sensitivity testing
• Multiple exclusion parameter combinations

The integration test follows established patterns in the repository and has been added to Group 2 in azure-pipelines.yml alongside similar database-related tests. Added proper dependency documentation in README.md indicating it depends on Install-SqlDscServer and Prerequisites, uses DSCSQLTEST instance, and creates test database and database principals.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

---

This change is 

[codecov]

Codecov Report

❌ Patch coverage is 66.66667% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 94%. Comparing base (11d39a0) to head (4f79f46).
⚠️ Report is 31 commits behind head on main.

Files with missing lines	Patch %	Lines
source/Public/Remove-SqlDscDatabase.ps1	66%	2 Missing ⚠️

Additional details and impacted files

@@         Coverage Diff          @@
##           main   #2260   +/-   ##
====================================
- Coverage    94%     94%   -1%     
====================================
  Files       149     149           
  Lines      9174    9180    +6     
====================================
+ Hits       8698    8702    +4     
- Misses      476     478    +2     

Flag	Coverage Δ
unit	94% <66%> (-1%)	⬇️

Files with missing lines	Coverage Δ
source/Public/Remove-SqlDscDatabase.ps1	84% <66%> (-5%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[johlju]

@copilot try again, you could not do the work due to a temporary glitch

[Copilot]

@copilot try again, you could not do the work due to a temporary glitch

I've successfully created the integration test for Test-SqlDscIsDatabasePrincipal command. The test covers all parameter combinations including database users, roles, fixed roles, and application roles with comprehensive error handling and edge cases. The test has been added to Group 2 in azure-pipelines.yml and the CHANGELOG.md has been updated. All syntax validation and unit tests pass successfully.

Commit: 46ddef7

[johlju]

For some reason this integration tests break the pipeline, it makes the pipeline fail at the end even though all tests passes. This error is output after the last test runs:

ERROR: Failed to connect to server runnervmshoy1\DSCSQLTEST.
At D:\a\1\s\output\RequiredModules\Sampler\0.118.3\tasks\Invoke-Pester.pester.build.ps1:911 char:9
+         Export-Clixml -Depth 5 -Path $PesterResultObjectCliXml -Force
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
At D:\a\1\s\output\RequiredModules\Sampler\0.118.3\tasks\Invoke-Pester.pester.build.ps1:422 char:1
+ task Invoke_Pester_Tests_v5 {
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Build FAILED. 5 tasks, 1 errors, 0 warnings 00:37:09.9530284
Export-Clixml : Failed to connect to server runnervmshoy1\DSCSQLTEST.
At D:\a\1\s\output\RequiredModules\Sampler\0.118.3\tasks\Invoke-Pester.pester.build.ps1:911 char:9
+         Export-Clixml -Depth 5 -Path $PesterResultObjectCliXml -Force
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Export-Clixml], ConnectionFailureException
    + FullyQualifiedErrorId : Microsoft.SqlServer.Management.Common.ConnectionFailureException,Microsoft.PowerShell.Co 
   mmands.ExportClixmlCommand
 
##[error]PowerShell exited with code '1'.

[johlju]

@johlju reviewed 9 of 9 files at r5, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @copilot)