stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity
Files
cf5b72974f923126944f4dcd47e85864ebb31a3b
git.stella-ops.org/docs/features/unchecked/vexlens/vexlens-truth-table-tests.md

1.4 KiB
Raw Blame History

VexLens Truth Table Tests

Status

NOT_FOUND

Description

Systematic truth table tests for VEX lattice merge correctness. The VexLens engine exists but comprehensive truth table test coverage is missing.

Why Not Implemented

  • No systematic truth table tests for VEX lattice merge correctness found
  • The VexLens test infrastructure does exist:
    • src/VexLens/__Tests/StellaOps.VexLens.Tests/ -- VexLens tests project
    • src/VexLens/StellaOps.VexLens/__Tests/StellaOps.VexLens.Tests/ -- additional test project
    • src/VexLens/StellaOps.VexLens/__Tests/StellaOps.VexLens.Core.Tests/ -- core tests
    • Tests cover: NormalizerTests, PurlParserTests, ProductMapperTests, CpeParserTests
    • src/VexLens/__Libraries/__Tests/StellaOps.VexLens.Spdx3.Tests/ -- SPDX3 integration tests
  • The VexLens engine has merge logic (consensus projections, delta computation) but does not have exhaustive truth table tests covering all VEX status transition combinations
  • TASKS.md files in test directories indicate planned but incomplete test coverage
  • The advisory called for systematic coverage of all status pairs (affected/not_affected/fixed/under_investigation x all transitions)

Source

  • Feature matrix scan

Notes

  • Module: VexLens
  • Modules referenced: src/VexLens
  • Related: src/VexLens/__Tests/ (existing tests cover parsing/mapping but not exhaustive lattice merge truth tables)