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
Back in February @danr raised an issue with AVA on how to get first-class support for tools like TestCheck.js. We've reached a consensus on implementing a t.try() assertion for which the calling code can determine whether to accept the results:
// pseudo-code for ava-check:functioncheck(genA,genB,implementation){returnasynct=>{while(true){constresult=awaitt.try(implementation,genA(),genB())if(result.passed||cannotMinimizeFurther()){returnresult.commit()}}}}
AVA recently stopped exposing its internal Test instance which has broken ava-check: avajs/ava#1835. Ideally we implement t.try() so TestCheck.js no longer has to rely on internals, but we need somebody to do the work. So, here's your call to action! Chime in on avajs/ava#1692 if you want to help out.
Many thanks!
The text was updated successfully, but these errors were encountered:
Hello 👋
Back in February @danr raised an issue with AVA on how to get first-class support for tools like TestCheck.js. We've reached a consensus on implementing a
t.try()
assertion for which the calling code can determine whether to accept the results:AVA recently stopped exposing its internal
Test
instance which has brokenava-check
: avajs/ava#1835. Ideally we implementt.try()
so TestCheck.js no longer has to rely on internals, but we need somebody to do the work. So, here's your call to action! Chime in on avajs/ava#1692 if you want to help out.Many thanks!
The text was updated successfully, but these errors were encountered: