Files
personaEngine2/tests/Unit/OutcomeExclusivity.Tests.ps1
T
dave cdc6bb33d3 Implement Stage A: rule engine, validation, audit, and safety gates
Completes 109 of 121 tasks. Every remaining task needs a tenant connection
(T055, T056, T101-T103) or an Azure Automation account (T115-T121).

  354 offline Pester tests      PASS
  Engine purity (Principle IV)  PASS
  Sanitization (SC-013)         PASS  (156 files)
  Graph module loaded in tests  none  (SC-008 holds)

What landed
  - Four-layer configuration validation with stable finding codes, covering
    every VR-002 and VR-003 condition, plus a 23-fixture invalid-config corpus
  - Run loop, audit records (NDJSON through a single sink), summaries,
    reconciliation, and exit codes 0-6
  - Persistence behind a single write-body builder whose result always has
    exactly one key
  - Invoke-PersonaEngine.ps1 and Edit-PersonaEngineConfig.ps1
  - Six docs, two pipelines, traceability matrix, V-5a and sanitization records

Three deviations from tasks.md, each recorded in its status block

  T033 is not in Resolve-UserPersona. evaluationErrorThreshold is run-level
  state and the rule engine is pure; a counter there would break Principle IV.
  It lives in New-PersonaRunCounter and is applied in the run loop.

  A new src/Engine/ layer holds Invoke-PersonaEngineRun. The entry script
  imports the manifest, which requires Microsoft.Graph.Authentication, so a
  loop living only inside it could not run on a machine without the Graph SDK
  and SC-004 could not be proven at all. The entry script is now a thin
  wrapper and what ships is what is tested.

  The invalid-config corpus is generated by a committed script, with the
  generated fixtures committed too, so a reviewer sees the fixture in the diff.

Defects found by running the code, not by reading it

  Group and role ID lists were double-wrapped: @(Get-PersonaGroupIdPage ...)
  around a comma-returned array collapsed every membership list into one
  bogus space-joined entry. That is a silent false non-match, exactly what
  FR-013 exists to prevent.

  A 403 whose status appears only in the exception message parsed as $null,
  which the retry policy treats as a transport error - five requests per
  account against a tenant already refusing. Status extraction now falls back
  to the message text, bounded to 400-599.

  The sanitization scan walked tracked files only, so it covered 34 of 156
  files and none of this phase's code. It now scans untracked non-ignored
  files too, and a negative control confirms it catches a planted leak.

  Test-Json reports one error per violating location, not first-failure-only
  as the V-5a draft claimed. Record and pin corrected.

Enforcement remains blocked on the V-4 security sign-off.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-20 21:48:19 -04:00

107 lines
4.8 KiB
PowerShell

#Requires -Modules @{ ModuleName = 'Pester'; ModuleVersion = '5.0.0' }
<#
SC-001: every processed user lands in exactly one outcome bucket.
Exclusivity is what makes reconciliation meaningful. If a user could be both
Matched and EvaluationError, the sum would still be checkable but would no longer
mean anything, and FR-021 would be verifying arithmetic rather than correctness.
#>
BeforeAll {
$repoRoot = Split-Path (Split-Path $PSScriptRoot -Parent) -Parent
. (Join-Path $repoRoot 'tests/TestHelpers.ps1')
foreach ($file in (Get-PersonaSourceFile -RepoRoot $repoRoot)) { . $file }
$script:target = 'extension_<EXTENSION-APP-ID>_<PERSONA>'
# A rule set that needs membership data, so a failed lookup produces
# EvaluationError and all three buckets are populated in one run.
$script:rules = @(
(New-TestMembershipRule)
[pscustomobject]@{
id = 'RULE-0900-EMPLOYEE'; name = 'Employees'; enabled = $true; priority = 900; persona = 'Employee'
match = [pscustomobject]@{
operator = 'all'
conditions = @([pscustomobject]@{ type = 'property'; property = 'Department'; operator = 'isNotNull' })
}
}
)
$script:config = New-TestRuntimeConfiguration -TargetAttribute $target -Rules $script:rules
}
Describe 'Exactly one outcome per user (SC-001)' {
BeforeEach {
Mock Write-Host { }
Mock Set-UserPersonaAttribute { [pscustomobject]@{ Succeeded = $true } }
Mock Get-PersonaUsers { New-TestPopulation -Count 24 -TargetAttribute $script:target }
# Every fourth account fails its membership lookup, producing a genuine mix
# of all three outcomes rather than a run where only one bucket is exercised.
$script:lookup = 0
Mock Get-PersonaGroupMembership {
$script:lookup++
($script:lookup % 4) -eq 0 `
? (New-PersonaMembershipRecord -DirectFailureReason 'Graph 503 after 5 attempts') `
: (New-PersonaMembershipRecord -AllRetrieved)
}
}
It 'accounts for every processed user across the three outcome buckets' {
$outcome = Invoke-PersonaEngineRun -Configuration $config -TargetAttribute $target `
-Context (New-TestAuditContext) -ShouldProcessGate { param($t, $d) $false }
$sum = $outcome.Counters.Matched + $outcome.Counters.Unclassified + $outcome.Counters.EvaluationError
$sum | Should -Be $outcome.Counters.Processed
}
It 'populates all three buckets, so the sum is not trivially satisfied' {
$outcome = Invoke-PersonaEngineRun -Configuration $config -TargetAttribute $target `
-Context (New-TestAuditContext) -ShouldProcessGate { param($t, $d) $false }
$outcome.Counters.Matched | Should -BeGreaterThan 0
$outcome.Counters.Unclassified | Should -BeGreaterThan 0
$outcome.Counters.EvaluationError | Should -BeGreaterThan 0
}
It 'accounts for every processed user across the action buckets too' {
$outcome = Invoke-PersonaEngineRun -Configuration $config -TargetAttribute $target `
-Context (New-TestAuditContext) -ShouldProcessGate { param($t, $d) $false }
$actions = $outcome.Counters.Unchanged + $outcome.Counters.WouldUpdate +
$outcome.Counters.Updated + $outcome.Counters.UpdateFailed + $outcome.Counters.Skipped
$actions | Should -Be $outcome.Counters.Processed
}
It 'assigns a single outcome value to each decision result' {
$record = New-PersonaUserRecord -AccountObjectId '00000000-0000-0000-0000-000000000101' `
-UserPrincipalName 'a@example.invalid' -Properties @{ Department = 'Finance' } `
-Membership (New-PersonaMembershipRecord -AllRetrieved)
$result = Resolve-UserPersona -UserRecord $record -Rules $script:rules
@($result.Outcome).Count | Should -Be 1
$result.Outcome | Should -BeIn @('Matched', 'Unclassified', 'EvaluationError')
}
It 'never reports an EvaluationError user as Matched' {
# The specific confusion FR-013 exists to prevent: an unevaluable account
# must never carry a persona, or the preserved value and the calculated value
# would both look authoritative.
$record = New-PersonaUserRecord -AccountObjectId '00000000-0000-0000-0000-000000000102' `
-UserPrincipalName 'b@example.invalid' -Properties @{ Department = 'Finance' } `
-StoredPersona 'Employee' `
-Membership (New-PersonaMembershipRecord -DirectFailureReason 'lookup failed')
$result = Resolve-UserPersona -UserRecord $record -Rules $script:rules
$result.Outcome | Should -Be 'EvaluationError'
$result.MatchedRuleId | Should -BeNullOrEmpty
$result.CalculatedPersona | Should -BeNullOrEmpty
$result.StoredPersona | Should -Be 'Employee'
}
}