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
{{ message }}
This repository has been archived by the owner on Aug 8, 2020. It is now read-only.
Given that this package wraps AVA's test & assertion interfaces, I wonder if we need to actually expose all interfaces.
E.g. AVA has callback tests (test.cb(t => { t.pass(); t.end() })). Does that make sense in BuckleScript?
Asynchronous tests need to be marked up as such in the syntax, and assertions over promises require throwsAsync / notThrowsAsync. Does BuckleScript have the concept of promises?
We should do what makes sense for BuckleScript, rather than try and be a perfect wrapper of AVA itself.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Given that this package wraps AVA's test & assertion interfaces, I wonder if we need to actually expose all interfaces.
E.g. AVA has callback tests (
test.cb(t => { t.pass(); t.end() })
). Does that make sense in BuckleScript?Asynchronous tests need to be marked up as such in the syntax, and assertions over promises require
throwsAsync
/notThrowsAsync
. Does BuckleScript have the concept of promises?We should do what makes sense for BuckleScript, rather than try and be a perfect wrapper of AVA itself.
The text was updated successfully, but these errors were encountered: