Added a new possible layout to the test data directory structure - if there is output-error file then the test will assert that there was an Err. Any panic should still fail the test, as we do no allow any panics in cdsl.
Added two new example tests where the schema should be treated as invalid.
Added documentation around tests.
This PR does not add many actual tests - these will come later, this PR only enables the developer to write such tests - did not want to mix different types of changes up in this PR.
Renamed output-uiobject.json file to output-uischema.json to be consistent with rjsf terminology.
Future work: right now these tests with invalid schemas test will accept any Err happily - there is a possibility that we will want to assert against Err contents in the future - the code introduced by this PR could be changed to get the contents of Err from the output-error file in such a case, if needed.
Added a new possible layout to the test data directory structure - if there is
output-errorfile then the test will assert that there was anErr. Anypanicshould still fail the test, as we do no allow any panics in cdsl.Added two new example tests where the schema should be treated as invalid.
Added documentation around tests.
This PR does not add many actual tests - these will come later, this PR only enables the developer to write such tests - did not want to mix different types of changes up in this PR.
Renamed
output-uiobject.jsonfile tooutput-uischema.jsonto be consistent withrjsfterminology.Future work: right now these tests with invalid schemas test will accept any
Errhappily - there is a possibility that we will want to assert againstErrcontents in the future - the code introduced by this PR could be changed to get the contents ofErrfrom theoutput-errorfile in such a case, if needed.See #16