so i think when actual is null, isActualDefined needs to be false

I disagree. It’s valid for the actual value to be

null

. That’s a distinct state from “there was no actual value”

yeah right, but it should not return null, but ValueWrapper(null)

Ah yes

pr is now updated to use AssertionFailedError directly.