Add integration test for ConvertTo-SqlDscEditionName command #2273
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
ConvertTo-SqlDscEditionNamecommand was missing integration test coverage to ensure reliability in real environments. This PR adds comprehensive integration tests that validate the command's functionality without requiring SQL Server connectivity.What's Added
Integration Test Coverage (
tests/Integration/Commands/ConvertTo-SqlDscEditionName.Integration.Tests.ps1):Pipeline Integration:
Testing
All 12 new integration tests pass, existing 3 unit tests continue to pass, and all 781 QA tests remain compliant. The integration test follows established repository patterns and provides real-environment validation for this utility command.
Fixes #2208.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.
This change is