Yes they are mostly inline with the rest. The only thing we need to change is initialize spec. I used to write those (there are probably still some other initialize specs here) just because heckle and then mutant needed those. I realized it makes no sense though because I do not want to test constructors as those are just methods that setup object's state and I don't want to write tests for object's attributes. This case is a bit different though as we have a configuration object and it's all about its attributes however I would not put the test for `coerce` option in the initialize spec anyway - I would put it probably in the call_spec. `call` should return the conf object, it's the expected behavior, and if you didn't tweak the coerce option inside the block then it must be set to true by default. This would be your test, maybe sth like that:

```ruby
subject { described_class.new.call(&block) }

context 'when coerce option wasn't explicitly set' do
  its(:coerce) { should be(true) }
end

context 'when coerce option was set explicitly to false' do
  its(:coerce) { should be(false) }
end
```

I can see that the second scenario is already taken care of in the current call_spec. So I'd suggest adding the first scenario and removing initialize_spec.