@benoittgt very kindly submitted a PR to fix some spacing issues in the markdown using gofmtmd.

It should be possible to automate this as part of the build script

Is your feature request related to a problem? Please describe.
Reading through what a fake can and can not do is not clear from the documentation.

Describe the solution you'd like
Exact methods that are available to a Fake need to be documented.

First of all thank you for Sinon, I believe the library is powerful and has helped me write a lot of tests. What I'm requesting here is

I have two setups, in one the -parallel option works just fine in vscode - it generates parallel test cases as it should. In the other it doesn't do anything (not reporting errors in custom flags is a problem in the vscode go plugin, which is not the issue here).

Both were installed with go get -u github.com/cweill/gotests/... when in the $HOME directory within 15 minutes of each other.

We've had these four methods as far back as NUnit source history goes. The double? overloads are the same as the first two overloads except that they throw InvalidOperationException if you pass null. Since they can't be used to pass null, they don't do anything that the safer double overloads don't do.

Should we obsolete them or fix them? What would fixing them look like?

name

Summary

The documentation "activate_announcer_on_command_failure" is not helpful for users as it misses information a