Freek is a platform for learning and sharing knowledge in the fields of software development, web development, and technology trends. Users can learn about software engineering best practices, programming languages, and emerging technologies, and share their experiences and insights with the community to foster learning and collaboration.

FREEK.DEV

The spatie/pest-plugin-route-testing package allows you to test all common routes in a Laravel app with a single test, simplifying the process of ensuring that pages work as intended. It supports testing specific routes, excluding certain routes, and working with route model bindings, thereby providing flexibility for developers. This package automates the testing of new pages, making it easier to maintain comprehensive test coverage.

How to make all routes in your Laravel app work by writing just a single test

Any test is better than no test, so use this as a way to get started from nothing.
However, automated testing like this comes with downsides that should be acknowledged:
Testing is documenting. Tests are a form of documentation or contract, that help define an app’s requirements. Abstracting this does not help the reader understand exactly what endpoints there are, their contexts, etc.
Tests are best when independent of implementations. Continuing the “contract” theme, tests are the most valuable when they have no dependency on the end implementation.
Here’s an example: if you have a route <code>/dashboard</code> that has been live for 6 months, your users are used to this URL. It might be bookmarked. If you rename this URL to <code>/home</code> (or change it accidentally), you want your test to break when <code>/dashboard</code> no longer works.
If you let your app define what routes it has available automatically by looking at the implementation (the route definitions), any changes will result in your tests still passing, even though the end user experience is worse. This is especially critical in APIs.
More code for specific situations. Once you need to do something more specific than lump routes together, you have to write more code using this library than a single test for a single route.
Basically, use libraries and abstractions until they start to get in your way. It’s better to go independent tests than try to jam a lot of custom functionality into a library meant to be universal and simple.