@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

If I create a test using a testcase source with a name "{m} (unique attribute)" and pass that test in through -testlist argument the test will not be discovered. If there is no space "{m}(unique attribute)" this works fine. The problem is in the TextRunner.MakeRunSetting when its building the prefilter list from the test list it is not trimming the sub string so the parent of the tests are not bei

Summary

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

Hello, and thank for this module.
I am wondering if consideration has been given to adding colour to the stack traces printed out upon failure of a test. For a test runner emphasizing colour, this seems like an obvious omission. I have patched in this functionality using pygments in my fork: psacawa/green@1922bc8 in an ad hoc fashion t