Problem
HealthTest-NtdsPathsLocation accepts expected database and log roots, but the normal built-in runner supplies neither.
File: health-tests/HealthTest-NtdsPathsLocation.ps1, lines 13-31.
With both lists empty, the code sets both checks to true and reports that the paths are sane without comparing them to anything.
Simple example
The intended database root is D:\NTDS, but the database is on C:\Windows\NTDS. A normal GetComputerHealth run supplies no expected root and reports PASS.
Expected behavior
Load the expected roots from documented configuration, define a meaningful default, or change the test into policy inventory whose wording does not claim validation.
Acceptance criteria
- PASS requires an actual documented comparison.
- A normal runner can receive configured roots.
- No baseline is reported as unconfigured, not sane.
- Unit tests cover matching, mismatching, and unconfigured baselines.
Problem
HealthTest-NtdsPathsLocationaccepts expected database and log roots, but the normal built-in runner supplies neither.File:
health-tests/HealthTest-NtdsPathsLocation.ps1, lines 13-31.With both lists empty, the code sets both checks to true and reports that the paths are sane without comparing them to anything.
Simple example
The intended database root is
D:\NTDS, but the database is onC:\Windows\NTDS. A normal GetComputerHealth run supplies no expected root and reports PASS.Expected behavior
Load the expected roots from documented configuration, define a meaningful default, or change the test into policy inventory whose wording does not claim validation.
Acceptance criteria