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
Hello, I have a question about the access to internal parts from test implementation. There were talks about public API available in #1692 and #1769. However, those features were not implemented yet, and in the mean time, before beta.5 there was access to instance of Test class if non-arrow function was passed as test implementation:
test('test case',function(t){console.log(this)})
This allowed me and testcheck-js (mentioned in #1692) to implement property testing and integrate it into ava.
However, with the change pushed into beta.5 (a681ecf), there is no way to access the instance anymore and hence not possible to act and affect the instance of Test and do things that are needed for property testing.
Would you consider reverting this change, before the public API is available? Furthermore, is it possible to not bind macros to null as well (runner.js#L269..L271), and bind it to instance of Test right before the execution of macros?
We have an open issue that will enable first-class support for tools like TestCheck.js. See #1692. I've put out a call with TestCheck.js as well: leebyron/testcheck-js#91
(I'm closing this issue for housekeeping purposes, but let's keep the conversation going.)
Description
Hello, I have a question about the access to internal parts from test implementation. There were talks about public API available in #1692 and #1769. However, those features were not implemented yet, and in the mean time, before
beta.5
there was access to instance ofTest
class if non-arrow function was passed as test implementation:This allowed me and testcheck-js (mentioned in #1692) to implement property testing and integrate it into ava.
However, with the change pushed into
beta.5
(a681ecf), there is no way to access the instance anymore and hence not possible to act and affect the instance ofTest
and do things that are needed for property testing.Would you consider reverting this change, before the public API is available? Furthermore, is it possible to not bind macros to
null
as well (runner.js#L269..L271), and bind it to instance ofTest
right before the execution of macros?Thank you!
Test Source
Config
Environment
The text was updated successfully, but these errors were encountered: