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
Currently 'tests' consist of working examples that are verified by visual inspection.
A useful addition would be tests that confirm that the json spec produced by a spec-generating function is what is expected. This would also allow documentation examples to be tested through elm-verify-examples.
We might also consider validating against Vega-Lite and Vega schemas, although there are still some cases where working VL/V examples can invalidate schemas.
The text was updated successfully, but these errors were encountered:
Perhaps, using elm-test could be a solution – the package looks rather straightforward to get started with. I have some experience with setting up Travis CI for the github repos, so can help a bit here.
Currently 'tests' consist of working examples that are verified by visual inspection.
A useful addition would be tests that confirm that the json spec produced by a spec-generating function is what is expected. This would also allow documentation examples to be tested through elm-verify-examples.
We might also consider validating against Vega-Lite and Vega schemas, although there are still some cases where working VL/V examples can invalidate schemas.
The text was updated successfully, but these errors were encountered: