Files
personaEngine2/tests/Unit/Pagination.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

127 lines
5.2 KiB
PowerShell

#Requires -Modules @{ ModuleName = 'Pester'; ModuleVersion = '5.0.0' }
<#
FR-004: @odata.nextLink is followed to exhaustion, and a truncated enumeration
raises rather than returning a partial population.
The second half is the one worth the effort. A partial population reconciles
cleanly, produces a plausible summary, and reports success - so nothing
downstream can tell that half the tenant was never looked at.
#>
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>'
}
Describe 'User enumeration pagination (FR-004)' {
It 'follows nextLink across every page' {
$script:page = 0
Mock Invoke-PersonaGraphRequest {
$script:page++
$users = 1..3 | ForEach-Object {
New-TestGraphUser -Id ('00000000-0000-0000-0000-{0:d12}' -f (($script:page - 1) * 3 + $_)) `
-UserPrincipalName ("user{0}-{1}@example.invalid" -f $script:page, $_)
}
$response = @{ value = $users }
if ($script:page -lt 4) { $response['@odata.nextLink'] = "/v1.0/users?`$skiptoken=page$script:page" }
$response
}
$result = @(Get-PersonaUsers -SelectProperties @('id', 'userPrincipalName'))
$result.Count | Should -Be 12
Should -Invoke Invoke-PersonaGraphRequest -Times 4 -Exactly
}
It 'stops when nextLink is absent rather than looping' {
Mock Invoke-PersonaGraphRequest { @{ value = @(New-TestGraphUser -Id '00000000-0000-0000-0000-000000000001' -UserPrincipalName 'a@example.invalid') } }
$result = @(Get-PersonaUsers -SelectProperties @('id'))
$result.Count | Should -Be 1
Should -Invoke Invoke-PersonaGraphRequest -Times 1 -Exactly
}
It 'raises on a response with no value collection rather than returning what it has' {
$script:page = 0
Mock Invoke-PersonaGraphRequest {
$script:page++
if ($script:page -eq 1) {
return @{
value = @(New-TestGraphUser -Id '00000000-0000-0000-0000-000000000001' -UserPrincipalName 'a@example.invalid')
'@odata.nextLink' = '/v1.0/users?$skiptoken=abc'
}
}
# Page two comes back malformed. Returning page one alone would look like
# a complete, tiny tenant.
@{ error = 'unexpected' }
}
{ @(Get-PersonaUsers -SelectProperties @('id')) } | Should -Throw -ExpectedMessage '*partial population*'
}
It 'raises on a null response' {
Mock Invoke-PersonaGraphRequest { $null }
{ @(Get-PersonaUsers -SelectProperties @('id')) } | Should -Throw
}
It 'requests the maximum page size so a large tenant needs fewer round trips' {
Mock Invoke-PersonaGraphRequest -ParameterFilter { $Uri -match '\$top=999' } -MockWith { @{ value = @() } }
$null = @(Get-PersonaUsers -SelectProperties @('id'))
Should -Invoke Invoke-PersonaGraphRequest -Times 1 -Exactly
}
}
Describe 'Membership pagination' {
It 'follows nextLink and collects only group objects' {
$script:page = 0
Mock Invoke-PersonaGraphRequest {
$script:page++
if ($script:page -eq 1) {
return @{
value = @(
@{ '@odata.type' = '#microsoft.graph.group'; id = '00000000-0000-0000-0000-0000000000a0' }
# An administrative unit arriving on memberOf. Treating it as
# a group ID would never match, which reads as "not a member".
@{ '@odata.type' = '#microsoft.graph.administrativeUnit'; id = '00000000-0000-0000-0000-0000000000e0' }
)
'@odata.nextLink' = '/v1.0/users/x/memberOf?$skiptoken=abc'
}
}
@{ value = @(@{ '@odata.type' = '#microsoft.graph.group'; id = '00000000-0000-0000-0000-0000000000b0' }) }
}
$record = Get-PersonaGroupMembership -UserObjectId '00000000-0000-0000-0000-000000000101' -NeedDirect
$record.DirectRetrieved | Should -BeTrue
$record.DirectGroupObjectIds.Count | Should -Be 2
$record.DirectGroupObjectIds | Should -Contain '00000000-0000-0000-0000-0000000000a0'
$record.DirectGroupObjectIds | Should -Contain '00000000-0000-0000-0000-0000000000b0'
$record.DirectGroupObjectIds | Should -Not -Contain '00000000-0000-0000-0000-0000000000e0'
}
It 'contains a mid-pagination failure to the affected facet instead of returning a short list' {
# The critical case. A truncated membership list looks exactly like a user who
# left a group, and would silently reclassify them (FR-013).
Mock Invoke-PersonaGraphRequest { throw 'Graph 503 after 5 attempts' }
$record = Get-PersonaGroupMembership -UserObjectId '00000000-0000-0000-0000-000000000101' -NeedDirect
$record.DirectRetrieved | Should -BeFalse
$record.DirectFailureReason | Should -Not -BeNullOrEmpty
}
}