Unified tests build and test

Entry/evidencePurpose
niseWrappers/wbf/CMakeLists.txtBuild/configuration entrypoint
niseCore/matcher/CMakeLists.txtBuild/configuration entrypoint
niseCore/sensor/CMakeLists.txtBuild/configuration entrypoint
niseCore/storage/CMakeLists.txtBuild/configuration entrypoint
doc/niseWrappers/wbf/Test/validation evidence
doc/tests/niseWrappers/wbf/Test/validation evidence
niseWrappers/wbf/tests/Test/validation evidence
niseCore/matcher/tests/Test/validation evidence
niseCore/sensor/tests/Test/validation evidence
niseCore/storage/tests/Test/validation evidence

Minimum validation

  1. Use the exact configured ref and compatible dependent refs.
  2. Build the narrowest affected target first.
  3. Run focused source-derived/unit tests where available.
  4. Run an exact customer build for interface or configuration changes.
  5. For driver/ABI/delivery changes, collect package, signing and integration evidence; unit success alone is insufficient.