DdddWith simplicity comes limitations, like with most things. RSpec makes it easy to do complex stubbing (mocking) as well as support numerous kinds of matchers that read well. Also keeping tests from spilling into other tests is a huge benefit to RSpec.

[253700ratchakon]

          With simplicity comes limitations, like with most things.  RSpec makes it easy to do complex stubbing (mocking) as well as support numerous kinds of matchers that read well.  Also keeping tests from spilling into other tests is a huge benefit to RSpec.

Before you fully commit to replacing RSpec, might be good to take one of two complex test cases from each RSpec file and make sure you can adequately replace them with minitest. Simplicity at the cost of functionality is not a good trade off. If minitest is going to make testing less reliable or function in a way that makes them less useful, that seems like a deal breaker.

Also the e2e tests in main OnDemand repo have to stay with Rspec cause there is simply no way to use minitest to replace beaker-rspec plugin.

Originally posted by @treydock in #844 (comment)

[johrstrom]

Not sure why you opened this, if it was an accident or what, but we are indeed moving to minitest instead of rspec.