@tenzan We're in kind of a unique time where Pest is becoming more popular but keep in mind it runs on top of PHPunit and that syntax is always supported, even with Pest. The fundamentals of testing don't change very often and I have rarely had to change tests due to Laravel upgrades. In fact the tests usually just help me know the upgrade went well.
Much like Eloquent is a layer on top of QueryBuilder that outputs SQL... Pest is just that same syntax-sugar chainable layer to make PHPunit tests more expressive / ultimately easier to write and memorize once you learn the syntax. Which really, for what most people test is like 10-15 methods (if that).
@fylzero I agree. The testing I learned for a "homebuilt" framework I work with is 100% transferable to testing in laravel. And laravel testing is the same; but better, since I started learning that a some years ago
How you guys learn/re-learn testing in Laravel, as sometimes it gets outdated depending on Laravel release?
@tenzan I can’t say I agree with this statement. Laravel uses PHPUnit for its test suite. PHPUnit hasn’t changed that much over the years. Tests look the same: you have classes, with methods for test cases, that call assertion methods (assertEquals etc).