In my opinion, practically, the testing paradigm (e2e < feature < unit) doesn't fit well with Laravel applications.
Feature tests better check ins and outs of your application. They're really handy when you're upgrading, refactoring the codebase, or adding/modifying features — even if you’re not familiar with the application.
If you've limited resources, I would suggest just focus on writing efficient and sufficient feature tests. There's no point in adding unit tests for the code that is already covered by feature tests.
I believe unit tests can be added later once feature tests are in place, but vice versa seems more difficult.
#Laravel #UnitVsFeatureTests
