-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accept interfaces instead of concrete *testing.T #50
Comments
The proposal sounds logical, but I am a bit vary of making the |
One big benefit of doing this is that it allows rapid to be more easily used when using a framework like ginkgo. The easiest way to do this in Ginkgo is to use See: |
Does f4756c7 look like a proper fix, or is anything still missing? |
Just checked it out on a test project, and this solution works perfectly (at least for my purposes using it with Ginkgo). Thanks a ton. |
Awesome, thanks! |
I've noticed that the concrete type
*testing.T
is used as argument in many places, likerapid.Check
. But in the implementation, it almost immediately callscheckTB
which converts it to the interfacetb
, which is a mirror ofTB
.We would like to be able to pass a
rapid.TB
instead of*testing.T
so that we can wrap the testing structure with additional information and behavior. Would you be opposed to changing the signature of the functions to acceptrapid.TB
instead of*testing.T
? I believe this would be a transparent change to the user given that*testing.T
satisfiesrapid.TB
. We'd be willing to do the work if approved.The text was updated successfully, but these errors were encountered: