mutant 0.8.6 → 0.8.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 56b2c2844f22529e172aac6c7042ba32e2213910
-  data.tar.gz: 69e3bed5fcbf29655a01aa99b32403bb7523e9d7
+  metadata.gz: 9f0d162e90a523f4f62c1f3541b1157fb78d6080
+  data.tar.gz: fa8dcc8abc2f6960ebd74a53711bf8e87ec0f32c
 SHA512:
-  metadata.gz: cf95681624f4a5796d0bd5134982084bae1437e3006acc7b43455230429558d8b558eaab5516371e58eb8d23ce4d2ac5cff4d43d0386149e59b26dd144459c10
-  data.tar.gz: 1b163c05a8afbaef8d97f3087aeedddd31615b7e7098eab3dbdb48efdd6dfe685eb60e092736ecbd58376cc77474f40a534bdfa4240d8b2992fc484ac76326d6
+  metadata.gz: 4c672d952620acf28cff4a26127a03facbc32c13bece89934b487433dc1fd2a918a76188fa0efe86588c7a480e8bf54383baa66eed869eeaf27752dce5ab313e
+  data.tar.gz: f3e533b36d8f52544523fbd81cda480a0653861106cf841420e11043a953c41a043e7a3b88fd8838629272d3bd960e76d22494bce9b7f014b10c67601d7a2c6e

data/Changelog.md

@@ -1,3 +1,7 @@
+# v0.8.7 2015-10-30
+
+* Fix blackliting regexp to correctly match the String `(eval)` absolutely.
+
 # v0.8.6. 2015-10-27
 
 * Add mutation from `Date.parse` to more strict parsing methods #448

data/README.md

@@ -21,30 +21,6 @@ to do its magic.
 
 Mutant does not have really good "getting started" documentation currently so please refer to presentations and blog posts below.
 
-Mutation-Operators:
--------------------
-
-Mutant supports a wide range of mutation operators. An exhaustive list can be found in the [mutant-meta](https://github.com/mbj/mutant/tree/master/meta).
-The `mutant-meta` is arranged to the AST-Node-Types of parser. Refer to parsers [AST documentation](https://github.com/whitequark/parser/blob/master/doc/AST_FORMAT.md) in doubt.
-
-There is no easy and universal way to count the number of mutation operators a tool supports.
-
-Presentations
--------------
-
-There are some presentations about mutant in the wild:
-
-* [RailsConf 2014](http://railsconf.com/) / http://confreaks.com/videos/3333-railsconf-mutation-testing-with-mutant
-* [Wrocloverb 2014](http://wrocloverb.com/) / https://www.youtube.com/watch?v=rz-lFKEioLk
-* [eurucamp 2013](http://2013.eurucamp.org/) / FrOSCon-2013 http://slid.es/markusschirp/mutation-testing
-* [Cologne.rb](http://www.colognerb.de/topics/mutation-testing-mit-mutant) / https://github.com/DonSchado/colognerb-on-mutant/blob/master/mutation_testing_slides.pdf
-
-Blog-Posts
-----------
-
-* http://www.sitepoint.com/mutation-testing-mutant/
-* http://solnic.eu/2013/01/23/mutation-testing-with-mutant.html
-
 Installation
 ------------
 
@@ -55,35 +31,7 @@ It'll pull the `mutant` gem (in correct version), that contains the main engine.
 gem install mutant-rspec
 ```
 
-The minitest integration is still in the [works](https://github.com/mbj/mutant/pull/330).
-
-The Crash / Stuck Problem (MRI)
--------------------------------
-
-Mutations generated by mutant can cause MRI to enter VM states its not prepared for.
-All MRI versions > 1.9 and < 2.2.1 are affected by this depending on your compiler flags,
-compiler version, and OS scheduling behavior.
-
-This can have the following unintended effects:
-
-* MRI crashes with a segfault. Mutant kills each mutation in a dedicated fork to isolate
-  the mutations side effects when this fork terminates abnormally (segfault) mutant
-  counts the mutation as killed.
-
-* MRI crashes with a segfault and gets stuck when handling the segfault.
-  Depending on the number of active kill jobs mutant might appear to continue normally until
-  all workers are stuck into this state when it begins to hang.
-  Currently mutant must assume that your test suite simply not terminated yet as from the outside
-  (parent process) the difference between a long running test and a stuck MRI is not observable.
-  Its planned to implement a timeout enforced from the parent process, but ideally MRI simply gets fixed.
-
-References:
-
-* [MRI fix](https://github.com/ruby/ruby/commit/8fe95fea9d238a6deb70c8953ceb3a28a67f4636)
-* [MRI backport to 2.2.1](https://github.com/ruby/ruby/commit/8fe95fea9d238a6deb70c8953ceb3a28a67f4636)
-* [Mutant issue](https://github.com/mbj/mutant/issues/265)
-* [Upstream bug redmine](https://bugs.ruby-lang.org/issues/10460)
-* [Upstream bug github](https://github.com/ruby/ruby/pull/822)
+The minitest integration is still in the [works](https://github.com/mbj/mutant/pull/445).
 
 Examples
 --------
@@ -100,6 +48,39 @@ mutant --include lib --require virtus --use rspec Virtus::Attribute.build
 mutant --include lib --require virtus --use rspec Virtus::Attribute#type
 ```
 
+Configuration
+-------------
+
+Occasionally mutant will produce a mutation with an infinite runtime. When this happens
+mutant will look like it is running indefinitely without killing a remaining mutation. To
+avoid mutations like this, consider adding a timeout around your tests. For example, in
+RSpec you can add the following to your `spec_helper`:
+
+```ruby
+config.around(:each) do |example|
+  Timeout.timeout(5_000, &example)
+end
+```
+
+which will fail specs which run for longer than 5 seconds.
+
+Rails
+-------
+
+To mutation test Rails models with rspec comment out ```require 'rspec/autorun'``` from your spec_helper.rb file.  Having done so you should be able to use commands like the following:
+
+```sh
+RAILS_ENV=test bundle exec mutant -r ./config/environment --use rspec User
+```
+
+Mutation-Operators:
+-------------------
+
+Mutant supports a wide range of mutation operators. An exhaustive list can be found in the [mutant-meta](https://github.com/mbj/mutant/tree/master/meta).
+The `mutant-meta` is arranged to the AST-Node-Types of parser. Refer to parsers [AST documentation](https://github.com/whitequark/parser/blob/master/doc/AST_FORMAT.md) in doubt.
+
+There is no easy and universal way to count the number of mutation operators a tool supports.
+
 Subjects
 --------
 
@@ -191,11 +172,55 @@ Mutation output is grouped by selection groups. Each group contains three sectio
    -----------------------
    ```
 
+Presentations
+-------------
+
+There are some presentations about mutant in the wild:
+
+* [RailsConf 2014](http://railsconf.com/) / http://confreaks.com/videos/3333-railsconf-mutation-testing-with-mutant
+* [Wrocloverb 2014](http://wrocloverb.com/) / https://www.youtube.com/watch?v=rz-lFKEioLk
+* [eurucamp 2013](http://2013.eurucamp.org/) / FrOSCon-2013 http://slid.es/markusschirp/mutation-testing
+* [Cologne.rb](http://www.colognerb.de/topics/mutation-testing-mit-mutant) / https://github.com/DonSchado/colognerb-on-mutant/blob/master/mutation_testing_slides.pdf
+
+Blog-Posts
+----------
+
+* http://www.sitepoint.com/mutation-testing-mutant/
+* http://solnic.eu/2013/01/23/mutation-testing-with-mutant.html
+
+The Crash / Stuck Problem (MRI)
+-------------------------------
+
+Mutations generated by mutant can cause MRI to enter VM states its not prepared for.
+All MRI versions > 1.9 and < 2.2.1 are affected by this depending on your compiler flags,
+compiler version, and OS scheduling behavior.
+
+This can have the following unintended effects:
+
+* MRI crashes with a segfault. Mutant kills each mutation in a dedicated fork to isolate
+  the mutations side effects when this fork terminates abnormally (segfault) mutant
+  counts the mutation as killed.
+
+* MRI crashes with a segfault and gets stuck when handling the segfault.
+  Depending on the number of active kill jobs mutant might appear to continue normally until
+  all workers are stuck into this state when it begins to hang.
+  Currently mutant must assume that your test suite simply not terminated yet as from the outside
+  (parent process) the difference between a long running test and a stuck MRI is not observable.
+  Its planned to implement a timeout enforced from the parent process, but ideally MRI simply gets fixed.
+
+References:
+
+* [MRI fix](https://github.com/ruby/ruby/commit/8fe95fea9d238a6deb70c8953ceb3a28a67f4636)
+* [MRI backport to 2.2.1](https://github.com/ruby/ruby/commit/8fe95fea9d238a6deb70c8953ceb3a28a67f4636)
+* [Mutant issue](https://github.com/mbj/mutant/issues/265)
+* [Upstream bug redmine](https://bugs.ruby-lang.org/issues/10460)
+* [Upstream bug github](https://github.com/ruby/ruby/pull/822)
+
 Planning a presentation?
 ------------------------
 
 Mutation testing lately (not only mutant) seems to attract some attention. So naturally
-people do talks about it at conferences, user groups or other chances. Thx for that!
+people do talks about it at conferences, user groups or other chances. Thanks for that!
 
 As I (the author @mbj) am not too happy with some of the facts being presented about
 mutant the last month.
@@ -204,29 +229,12 @@ So if you plan to do a presentation: I offer to review your slides / talk - for
 My intention is NOT to change your bias pro / against this tool. Just to help to fix
 invalid statements about the tool.
 
-Also in many cases a conversation to the author, should help you to imporve the talk
+Also in many cases a conversation to the author should help you to improve the talk
 significantly. One of mutants biggest weaknesses is the bad documentation, but instead of
 assumptions based on the absence of docs, use the tool authors brain to fill the gaps.
 
 Hint, same applies to papers.
 
-Rails
--------
-
-Assuming you are using rspec, you can mutation test Rails models by adding the following lines to your Gemfile:
-
-```ruby
-group :test do
-  gem 'mutant-rspec'
-end
-```
-
-Next, run bundle and comment out ```require 'rspec/autorun'``` from your spec_helper.rb file.  Having done so you should be able to use commands like the following:
-
-```sh
-RAILS_ENV=test bundle exec mutant -r ./config/environment --use rspec User
-```
-
 Support
 -------
 
@@ -237,9 +245,8 @@ Your options:
 * [GitHub Issues](https://github.com/mbj/mutant/issues)
 * Ping me on [twitter](https://twitter.com/_m_b_j_)
 
-There is also the [#mutant](http://irclog.whitequark.org/mutant) channel on freenode.
-As my OSS time budged is very limited I cannot join it often. Please prefer to use GitHub issues with
-a 'Question: ' prefix in title.
+There is also a mutant [slack chat](https://mutation-testing.slack.com/).
+@mention [@\_m\_b\_j\_](https://twitter.com/_m_b_j_) on twitter for an invite.
 
 Credits
 -------

data/lib/mutant/matcher/method.rb

@@ -7,7 +7,7 @@ module Mutant
 
       # Methods within rbx kernel directory are precompiled and their source
       # cannot be accessed via reading source location. Same for methods created by eval.
-      BLACKLIST = %r{\Akernel/|(eval)}.freeze
+      BLACKLIST = %r{\A(kernel/|\(eval\)\z)}.freeze
 
       # Enumerate matches
       #

data/lib/mutant/version.rb

@@ -1,4 +1,4 @@
 module Mutant
   # Current mutant version
-  VERSION = '0.8.6'.freeze
+  VERSION = '0.8.7'.freeze
 end # Mutant

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: mutant
 version: !ruby/object:Gem::Version
-  version: 0.8.6
+  version: 0.8.7
 platform: ruby
 authors:
 - Markus Schirp
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-10-27 00:00:00.000000000 Z
+date: 2015-10-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: parser