Unified tests component interactions

flowchart LR
  Spec[Markdown test specification] --> Discover[pipeline discovery]
  Ref[Target repository + ref] --> Variant[Variant resolver]
  VariantMap[variant_map.json] --> Variant
  Discover --> Extract[Extract target functions]
  Ref --> Extract
  Variant --> Overrides[WinTypes / mocks / test overrides]
  Extract --> Build[CMake or Make build]
  Overrides --> Build
  Build --> Run[GTest / virtual test execution]
  Run --> Parse[Result and case parser]
  Parse --> CI[GitHub Actions / Jenkins evidence]
  CI --> Publish[Artifacts and Wiki/dashboard publication]

The arrows show dependency or runtime/control flow supported by the source structure and entrypoints at bd7ceb867928. Dotted arrows mean configuration or validation rather than a runtime call.

Interaction contracts

From/toContract
Test specificationsStores Markdown cases and generated/executable virtual-test harnesses.
PipelineDiscovers folders, resolves variants, extracts source, builds targets, runs tests and parses results.
Variant modelMaps target source branches to compatible test environments and overrides.
niseCore suitesBuilds focused GTest/GMock targets around extracted or preprocessed production functions.
WBF suiteExtracts CBiometricDevice capture/wake functions and generates customer property headers.
CI workflowsRuns PR/push unit, actual and virtual tests and publishes evidence.
Source mappingMaps test scopes to source repositories/default refs.
Published branchCarries the repository overview and selected publishing/workflow infrastructure, not the full dev test tree.

Evidence