#redirect_to(url_or_description, &block) ⇒ RedirectToMatcher

The redirect_to matcher tests that an action redirects to a certain
location. In a test suite using RSpec, it is very similar to
rspec-rails's redirect_to matcher. In a test suite using Minitest +
Shoulda, it provides a more expressive syntax over
assert_redirected_to.

#render_template(options = {}, message = nil) ⇒ RenderTemplateMatcher

The render_template matcher tests that an action renders a template
or partial. In RSpec, it is very similar to rspec-rails's
render_template matcher. In a test suite using Minitest + Shoulda, it
provides a more expressive syntax over assert_template.

#route(method, path, port: nil) ⇒ RouteMatcher

The route matcher tests that a route resolves to a controller,
action, and params; and that the controller, action, and params
generates the same route. For an RSpec suite, this is like using a
combination of route_to and be_routable. In a test suite using
Minitest + Shoulda, it provides a more expressive syntax over
assert_routing.

You can use this matcher either in a controller test case or in a
routing test case. For instance, given these routes:

Notice that in the former case, as we are inside of a test case for
PostsController, we do not have to specify that the routes resolve to
this controller. In the latter case we specify this using the
controller key passed to the to qualifier.

Specifying a port

If the route you're testing has a constraint on it that limits the route
to a particular port, you can specify it by passing a port option to
the matcher: