Test-SqlDscDatabaseProperty: Validate SQL Server database properties

.github/instructions/SqlServerDsc-guidelines.instructions.md

@@ -27,7 +27,6 @@ applyTo: "**"
 ## SQL Server Interaction
 - Always prefer SMO over T-SQL
 - Unit tests: Use SMO stub types from SMO.cs, never mock SMO types
-- Run tests in new session after changing SMO.cs
 
 ## Testing CI Environment
 - Database Engine: instance `DSCSQLTEST`

.github/instructions/dsc-community-style-guidelines-pester.instructions.md

@@ -52,10 +52,11 @@ applyTo: "**/*.[Tt]ests.ps1"
 - Public commands: `tests/Unit/Public/{Name}.Tests.ps1`
 - Private functions: `tests/Unit/Private/{Name}.Tests.ps1`
 
-## Data-Driven Tests
-- Define variables in separate `BeforeDiscovery` for `-ForEach` (close to usage)
+## Data-Driven Tests (Test Cases)
+- Define `-ForEach` variables in `BeforeDiscovery` (close to usage)
 - `-ForEach` allowed on `Context` and `It` blocks
-- Keep scope close to usage context
+- Never add `param()` inside Pester blocks when using `-ForEach`
+- Access test case properties directly: `$PropertyName`
 
 ## Best Practices
 - Cover all scenarios and code paths

.github/instructions/dsc-community-style-guidelines-powershell.instructions.md

@@ -188,7 +188,7 @@ function Get-Something
 - Parameter type on line above parameter name
 - Parameters separated by blank line
 - Parameters should use full type name.
-- Pipeline parameters (`ValueFromPipeline = $true`) must be declared in ALL parameter sets
+- `ValueFromPipeline` must be consistent across all parameter sets declarations for the same parameter
 
 ## Best Practices
 

.vscode/settings.json

@@ -91,7 +91,23 @@
         "SOURCEBRANCHNAME",
         "setvariable",
         "RAISERROR",
-        "filegroup"
+        "filegroup",
+        "checkdb",
+        "msdb",
+        "db_datawriter",
+        "db_ddladmin",
+        "db_owner",
+        "db_accessadmin",
+        "db_securityadmin",
+        "db_backupoperator",
+        "db_denydatareader",
+        "db_denydatawriter",
+        "OLTP",
+        "LCID",
+        "varchar",
+        "maxdop",
+        "hotfixes",
+        "checkpointing"
     ],
     "cSpell.ignorePaths": [
         ".git"

CHANGELOG.md

@@ -93,6 +93,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Added integration tests for `Test-SqlDscIsDatabasePrincipal` command to ensure
   it functions correctly in real environments
   [issue #2231](https://github.com/dsccommunity/SqlServerDsc/issues/2231).
+- Added public command `Test-SqlDscDatabaseProperty` to test database properties
+  on SQL Server Database Engine instances. This command supports two parameter sets:
+  `ServerObject` with **DatabaseName**, and `DatabaseObject` (from `Get-SqlDscDatabase`).
+  It allows users to specify any non-collection properties of the SMO Database object
+  as dynamic parameters to test, returning `$true` if all tested properties match
+  their expected values, and `$false` otherwise. This command improves maintainability
+  of SQL DSC resources and provides granular database configuration testing
+  [issue #2306](https://github.com/dsccommunity/SqlServerDsc/issues/2306).
 
 ### Fixed
 

azure-pipelines.yml

@@ -337,6 +337,7 @@ stages:
                   'tests/Integration/Commands/New-SqlDscDatabase.Integration.Tests.ps1'
                   'tests/Integration/Commands/Set-SqlDscDatabase.Integration.Tests.ps1'
                   'tests/Integration/Commands/Test-SqlDscDatabase.Integration.Tests.ps1'
+                  'tests/Integration/Commands/Test-SqlDscDatabaseProperty.Integration.Tests.ps1'
                   'tests/Integration/Commands/Get-SqlDscDatabasePermission.Integration.Tests.ps1'
                   'tests/Integration/Commands/Set-SqlDscDatabasePermission.Integration.Tests.ps1'
                   'tests/Integration/Commands/ConvertTo-SqlDscDatabasePermission.Integration.Tests.ps1'