Tim Chambers

``` before do allow(I18n).to receive(:t) do |selector, options| expect(selector).not_to be_frozen end.and_call_original end ``` appears not to be valid syntax according to @myronmarston https://github.com/rspec/rspec-mocks/issues/774 myronmarston commented on Sep 2, 2014 The...

I didn't expect such a rapid snippet of code to be tested at all. Amazing how fast you came up with it. :) That's why I tested it in my...

FYI here is what I came up with to define expectations of parameters to I18n.t that does the job for me: ``` def unfrozen_string satisfy { |*arg| !arg.first.frozen? } end...

The more I think about this issue, the more I feel as though my performance I experience with mutant is a direct reflection of MY fundamental lack of understanding of...

No attempt to hurry you - take your time. I feel like this is my failing so I wanted to declare that and include the context so I am not...

Please do not read till you are back from holiday! I did a rough non-scientific test yesterday of my hypothesis that the number of specs defined in my app correlate...

My inference from further experimentation in this area is that there are a number of MY contextual settings that conspire to degrade the performance of mutation testing in my situation....

@mbj No problem - my workaround works and is saving me loads of time. I will add that unless I am missing something I could do already, I consider this...

Perhaps I wasn't clear. My issue is not that I expect to have the validations mutated - quite the contrary. I only expect the source in the current source file...

@mockdeep Thanks for the reply. You ARE hearing me say I do not _think_ the validations are running during my mutations. It could be any of the options you portrayed....