As I mentioned above, in the end I abandoned the idea of automatically verifying only the routes in the routes file, and instead coded a test for each route so that tests would start failing if breaking changes were made to the routes file…
]]>I have now cleared out my files and will start again tomorrow. I think it should work then :)
]]>Now that we’re a few months down the road, were you able to solve this in the end?
Thanks for your post :)
]]>As for your point about the first option, I agree that disabling all middleware during testing could lead to a slew of issues. But I just meant that you could choose not to use the LaravelLocalizationRedirectFilter middleware in your application. This would lead to having the routes /about
and /en/about
both work and both show the same thing, instead of having /about
issue a redirect to /en/about
. But I don’t think it would cause any of the other problems you mention, would it?