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
It is currently possible to have assertions that run after the test that defined them, and at that point, ospec is unacle to trace their origin.
One possibility to solve this would be to change the API to something tape-like:
o("test",o=>{// this would either refuse to worksetTimeout(()=>o(1).equals(false),5)})
If we were to implement this, we'd need a complimentary codemod to upgrade the test suites. If someone skilled in theses want to step up and write it would be most welcome. Otherwise I'll dive into it.
The text was updated successfully, but these errors were encountered:
I'm in the process of implementing this as an opt-in, run-time option. I'll provide o.localAssertions and o.localAssertions which can be nested. o.localAssertions(true) at the root of a test suite will also be valid as a global switch.
It is currently possible to have assertions that run after the test that defined them, and at that point, ospec is unacle to trace their origin.
One possibility to solve this would be to change the API to something tape-like:
If we were to implement this, we'd need a complimentary codemod to upgrade the test suites. If someone skilled in theses want to step up and write it would be most welcome. Otherwise I'll dive into it.
The text was updated successfully, but these errors were encountered: