Null is explicitly disallowed in most field constructors. Thus the random results of passing null are undefined and may change. These changes should not be tested against.
Exceptions: Variable and serializable lable fields acually do take null.
This commit is due to the upcoming parseInt->Number commit which happens to change how null behaves.
Also added missing ‘empty’ test for checkboxes.