Add Minitest invocation alongside RSpec in basic-setup.md

Step 5 currently shows only `bundle exec rspec` for running tests on
both sides. Add a short note that Minitest apps substitute
`bin/rails test` (or `rake test`), and show the Minitest equivalent
block alongside the RSpec one. Point to `workflows/setup-workflow.md`
Step 11 for the full test-runner detection logic (RSpec, Minitest,
`bin/test` wrapper, `parallel_tests`, `turbo_tests`).

Author: JuanVqz

dual-boot/examples/basic-setup.md

@@ -71,6 +71,10 @@ BUNDLE_GEMFILE=Gemfile.next bundle install
 
 ### 5. Run Tests Against Both
 
+This example uses RSpec. If your project uses Minitest, substitute `bin/rails test` (or `rake test`) for `bundle exec rspec` throughout. The `BUNDLE_GEMFILE=Gemfile.next` prefix works with any test runner. See `workflows/setup-workflow.md` Step 11 for the full detection logic (RSpec, Minitest, `bin/test`, `parallel_tests`, `turbo_tests`).
+
+**RSpec:**
+
 ```bash
 # Current version (4.2)
 bundle exec rspec
@@ -81,6 +85,16 @@ BUNDLE_GEMFILE=Gemfile.next bundle exec rspec
 # => Some failures — fix using NextRails.next? branching
 ```
 
+**Minitest equivalent:**
+
+```bash
+# Current version (4.2)
+bin/rails test
+
+# Next version (5.0)
+BUNDLE_GEMFILE=Gemfile.next bin/rails test
+```
+
 ### 6. Fix a Breaking Change
 
 On Rails 4.2, `ActionController::TestRequest.new` takes an optional `env`. On 5.0, `new` requires two non-optional arguments (so the 4.2 call raises `ArgumentError`), and 5.0 introduces `TestRequest.create` — which doesn't exist on 4.2 (`NoMethodError`). Each side raises on the other. A conditional is required: