Andy Waite
Andy Waite
@Manfred rubocop-rails is already supported: https://github.com/codeclimate/codeclimate-rubocop/issues/178
https://github.com/rubocop-hq/minitest-style-guide/pull/35
There no such method in minitest, it's added by other libraries, e.g. https://www.rubydoc.info/gems/minitest-rails-shoulda/0.4.1/MiniTest%2FAssertions%3Aassert_same_elements
I think this would be a great addition. I frequently refer to @jdkaplan's [original post](https://jdkaplan.dev/blog/learn-sorbet-in-y-minutes/) for reference.
For reference, it was Rails 5 when controller tests were deprecated: https://blog.bigbinary.com/2016/04/19/changes-to-test-controllers-in-rails-5.html
@pirj I've suggested this as a cop for rubocop-rails: https://github.com/rubocop-hq/rubocop-rails/issues/20
As a possible reference: > RSpec is capable of running your specs in :random order, and we generally recommend you do that. Effective Testing with RSpec 3, Chapter 8
For reference, here's where this was added: https://github.com/rspec/rspec-core/commit/7b0d232
Oh, interesting. It seems RSpec own suite started using that in https://github.com/rspec/rspec-core/commit/82bf93e6e2eac8a20d6d34c6b0a8f6ccb874628a (March 2010), which was far before https://github.com/rspec/rspec-rails/pull/1137. I suspect many most non-Rails projects don't do this, but I...
Fair point. I'll think about how to phrase it.