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

This is a corner case that I only ran into in due to work on the analyzers in nunit/nunit.analyzers#54, and my guess is that very few will run into this problem. Nevertheless, I think we could improve the error message, and fix seems simple and safe.

Given a generic test method with no parameters we get a failure that is difficult to interpret for the users (see last example below for more deta

Summary

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

Seems that adding -e also suppress the exception name and cause. It would be great to keep them while supressing the traceback

Example with Arpeggio library:

Failure in tests.unit.test_promql.TestPromQLConversion.test_conversion (expr='sum by(pod)(rate(metric_test_app[2m] * 60)')
  File "/Users/ocervello/Workspace/dev/cloudops-migrator/tests/unit/test_promql.py", line 39, in test_con