Don't use a positive `raise_error` expectation without specifying the error type expected
RSpec warning:
WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives,
since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially
allowing the expectation to pass without even executing the method you are intending to call. Actual error
raised was #<Exception: Other error message>. Instead consider providing a specific error class or message.
This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`.
Called from /Users/tsigo/Code/gitlab/gdk-ce/gitlab-ce/spec/services/projects/destroy_service_spec.rb:149
We should be doing something like
expect do
Sidekiq::Testing.inline! { destroy_project(project, user, {}) }
end.to raise_error(Exception, 'Other error message')