Add integration test for Get-SqlDscStartupParameter command

[Copilot]

• Analyze the repository structure and understand the existing codebase
• Review the Get-SqlDscStartupParameter function and its requirements
• Examine existing integration test patterns and templates
• Verify the build system and unit tests work correctly
• Create integration test file following project guidelines and patterns
• Implement test scenarios for both parameter sets (ByServerName and ByServiceObject)
• Test with different instances and error conditions
• Add entry to integration test workflow in azure-pipelines.yml
• Update CHANGELOG.md with the new test coverage
• Update integration tests README with documentation
• Validate that the test syntax is correct and follows repository patterns
• Address reviewer feedback: fix error message, remove service management, add blank line
• Fix StartupParameters type access using InModuleScope pattern
• Add -ModuleName parameter to all InModuleScope calls

✅ Implementation Complete with All Feedback Addressed

Successfully implemented comprehensive integration test coverage for Get-SqlDscStartupParameter command and addressed all reviewer feedback including proper module scoping for InModuleScope calls.

Latest Fix Applied

• ✅ Added -ModuleName $script:moduleName parameter to all 5 InModuleScope calls
• ✅ Ensures proper module context when accessing the StartupParameters class in integration tests
• ✅ Follows the same pattern used in unit tests but with explicit module naming for integration tests

All Reviewer Feedback Addressed

• ✅ Changed error message task from 'build' to 'noop'
• ✅ Removed Start-Service call (service already started by dependencies)
• ✅ Removed Stop-Service call (service must remain running for other tests)
• ✅ Added blank line at end of file per project standards
• ✅ Removed empty AfterAll block to eliminate PSScriptAnalyzer warning
• ✅ Fixed module class type access using proper scoping with InModuleScope
• ✅ Added explicit -ModuleName parameter to all InModuleScope calls

Test Coverage

• Parameter Sets: Both ByServerName and ByServiceObject with all parameter combinations
• Error Handling: Non-existent instances, wrong service types, invalid objects
• Output Validation: Correct StartupParameters object with proper property types
• Pipeline Support: Testing pipeline input for ServiceObject parameter
• Cross-Validation: Ensuring both parameter sets return identical results

Quality Assurance

• ✅ Zero PSScriptAnalyzer issues after all fixes
• ✅ Follows established integration test patterns with proper module scoping
• ✅ Uses proper error handling with -ErrorAction 'Stop'
• ✅ Includes verbose logging and proper test structure
• ✅ Uses DSCSQLTEST instance as per integration test guidelines
• ✅ Service lifecycle properly managed (no start/stop, leaves running)
• ✅ Module class types accessed correctly with explicit module naming

The integration test validates the command works correctly in a real SQL Server environment and complements the existing unit test coverage perfectly.

Fixes #2217.

---

💡 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

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94%. Comparing base (11d39a0) to head (bde0611).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@         Coverage Diff          @@
##           main   #2249   +/-   ##
====================================
- Coverage    94%     94%   -1%     
====================================
  Files       149     149           
  Lines      9174    9174           
====================================
- Hits       8698    8697    -1     
- Misses      476     477    +1     

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

Files with missing lines	Coverage Δ
source/Public/Get-SqlDscStartupParameter.ps1	96% <100%> (-4%)	⬇️

🚀 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]

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