I really like how simple @_m_b_j_ made specifying mutations for mutant. This code specifies what mutations are generated for `foo[1]`.pic.twitter.com/GjvVHOPCyH
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
rubocop-rspec's declarative tests are so nice that I've considered writing a script to just fill in documentation examples from our tests.
Why write docs (that basically looks the same as these tests) when you can just use the tests that you know are going to be correct.
The rubocop-rspec tests are strong too. They specify: * Offending code * Offending column ranges * # of offenses * Message for each offense
Likewise, the mutant tests specify exactly what mutations are generated. Missing mutations and unexpected mutations both fail the tests.
These are unit tests too. The rubocop-rspec passes asserts offenses from one class. Mutant invokes a mutator class. High level but isolated.
"Follow pain of your tests" they say. These allow quicker feature development with better coverage though. Sometimes pain is just friction.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.