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
However it calls testing.M.Run(), I'm not sure this adds anything useful, in our case it's even detrimental as it does not handle the situation well when running with Go's -race option in combination with the env variable GORACE=exitcode=0.
Also it always seems to cause warning of :
...
testing: warning: no tests to run
...
For now I've removed it in our case, is there any side-effect to this?
The text was updated successfully, but these errors were encountered:
Good question, to be honest, I'm not sure why that is in the FAQ.
testing.M.Run() would execute all tests in your pkg, so I would assume it was added to the FAQ to show how you can execute godog next to your normal tests.
in the faq there is an example of TestMain
However it calls
testing.M.Run()
, I'm not sure this adds anything useful, in our case it's even detrimental as it does not handle the situation well when running with Go's-race
option in combination with the env variableGORACE=exitcode=0
.Also it always seems to cause warning of :
For now I've removed it in our case, is there any side-effect to this?
The text was updated successfully, but these errors were encountered: