I think it depends on the scale of your opplication, and its architecture.
-
if you are using Laravel structure, controller with controllers, model with models..ect its better to test accordingly and test controller methods, tests/Feature/Http/Controllers/OrderControllerTest ..ect like Jason McCreary suggests Confident-Laravel course.
-
If instead there more logic outside the controllers, which is really recommended you would for example test middlewares in a unit tests, and try to make a feature test. like Adam Wathan TDD course says.
-
if its a DDD project, actions are very easily unit tested, and overall you will deal with a fairly smaller classes and tests. like Spatie team would for a big project.
you can find all this courses source code open source on github.