@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.

If you want to use sinon with mocha, you shouldn't forget to restore the sinon sandbox after each test. This is documented here in general setup.

Since version 7.2, mocha supports root hooks. It is a way to export mocha root hooks (beforeEach, afterEach etc) fr

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.

I believe a couple Warn.If overloads have incorrect summary comments.

https://github.com/nunit/nunit/blob/master/src/NUnitFramework/framework/Warn.cs#L335

https://github.com/nunit/nunit/blob/master/src/NUnitFramework/framework/Warn.cs#L335

The summary comments on those overloads read:

Asserts that a condition is true. If the condition is false, a warning is issued.

However, the

Summary

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