I understand the reasoning behind the documentation for i_suck_and_my_tests_are_order_dependent. However I feel that this method name and its comment are glib and do not provide adequate rationale for why tests should be order independent. Nor does it allow for the possibility that there are a very limited number of legitimate reasons to want tests to be run sequentially, particularly when deali

In the following scenario, replacing the body of Child#one with super causes a SystemStackError when Child#one is being called. However mutant does not detect that this error kills the mutation that replaces the method's body with super. See https://github.com/matthias-g/mutant_super_bug for a running example.

class Parent
  attr_reader :foo

  def initialize(foo)
    @foo = fo

From [this comment][3]:

I looked up the YARD docs for a @param tag and was surprised to see that the order should be: [@param name [Types] description][1]. I noticed that all of the Mocha YARD docs use @param [Types] name description which seems odd. I trawled through the historical YARD documentation, CHANGELOG, and issues and [eventually discovered][2] that although the documented o

Summary

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

It seems like the documentation on shrinking is outdated: Array isn't monkey patched any more and the retry? function now needs to be implemented.

The extension is currently untested, I should really add tests to make sure things don't break when I change things.

It would be nice to have documentation on how to install and run this gem. Even better to have additional info about limitations and usage.