test-driven-development

@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.
Today we silently ignore stubbing issues, such as trying to use sinon.stub(obj, 'prop'), when obj.prop is a synthetic getter. From a user perspective, it is probably more user friendly to be explicitly told immediately that this Object.descriptor is non-configurable (perhaps even with a link to a Sinon doc page!) and cannot be

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.

The NUnitEqualityComparer contains an optional parameter in the public API to specify if the comparison is top-level or not.
https://github.com/nunit/nunit/blob/8de9af1d695d42d2d85604a100ff9f6c00e5728f/src/NUnitFramework/framework/Constraints/NUnitEqualityComparer.cs#L157

This has been converted to separate overloads in a subsequent PR. nunit/nunit#3406

That PR also

Summary

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