Exclude methods defined in lexical scope of class_eval / instance_eval / *_eval from automated subject matching. #254
Labels
Comments
mbj
added a commit
that referenced
this issue
Sep 16, 2014
* No easy way to insert mutants on these via current monkey patching loader * The blocks are typically part of a method building library when those libraries are mutated the def/defs nodes will be part of an mutated block that is included in a subject. [fix #254]
mbj
added a commit
that referenced
this issue
Sep 16, 2014
* No easy way to insert mutants on these via current monkey patching loader * The blocks are typically part of a method building library when those libraries are mutated the def/defs nodes will be part of an mutated block that is included in a subject. [fix #254]
mbj
added a commit
that referenced
this issue
Sep 16, 2014
* No easy way to insert mutants on these via current monkey patching loader * The blocks are typically part of a method building library when those libraries are mutated the def/defs nodes will be part of an mutated block that is included in a subject. [fix #254]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When mutating an active record based project I found alive mutants that cannot easily be killed.
Models got alive mutants in:
https://github.com/rails/rails/blob/v4.1.5/activerecord/lib/active_record/associations/builder/belongs_to.rb#L31-L70
Mutations for these methods inside
*_evalbodies in block form are not correctly inserted via monkeypatching. There might be a chance to do this but it is unlikely such code is a valid mutation subject for an app using active record.Such methods should IMO be unit tested / covered form the library, NOT from the clients code. So it'll probably be saved to exclude them from mutation from client.
The text was updated successfully, but these errors were encountered: