You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've found that a prop in two unit tests is spelled with incorrect case (uses camelCase instead of lowercase), which results in a false-positive test because the mocked prop is simply not used. If the case is fixed, the tests fail.
In the following two unit tests, the mocked prop uiSchema is passed into the FormBuilder component, however since the prop must match in case, it is not used by FormBuilder because it is expecting all lowercase uischema.
When correcting the case of this prop, the tests fail, because it seems that some fields are being flagged as "unrecognized properties". Example: "Unrecognized UI schema property: newInput1".
Note: It's not clear whether the mocks are simply incorrect on these tests, or if there truly is a missed error.
The text was updated successfully, but these errors were encountered:
I've found that a prop in two unit tests is spelled with incorrect case (uses camelCase instead of lowercase), which results in a false-positive test because the mocked prop is simply not used. If the case is fixed, the tests fail.
In the following two unit tests, the mocked prop
uiSchema
is passed into the FormBuilder component, however since the prop must match in case, it is not used by FormBuilder because it is expecting all lowercaseuischema
.False positive tests:
When correcting the case of this prop, the tests fail, because it seems that some fields are being flagged as "unrecognized properties". Example: "Unrecognized UI schema property: newInput1".
Note: It's not clear whether the mocks are simply incorrect on these tests, or if there truly is a missed error.
The text was updated successfully, but these errors were encountered: