This spec never calls `configure_default_syntax`.  That's a problem, because the deprecation warning is only printed on the first usage of `should` after the default has been configured.  As a result, this spec could pass even w/o the `@warn_about_should = false` logic if the last spec that ran was something like:

``` ruby
        it 'messes it up' do
          configure_default_syntax
          3.should eq(3)
        end
```

I think that to ensure there's no false positive, you have to explicitly call `configure_default_syntax` so that you control when that is called relative to the logic here.