Laravel Testing 21/24: What is PEST and How It Works

Link to the full course: laraveldaily.c...
- - - -
Support the channel by checking out my products:
My Laravel courses: laraveldaily.c...
Laravel QuickAdminPanel: quickadminpane...
Livewire Kit Components: livewirekit.com
- - - -
Other places to follow:
My weekly Laravel newsletter: us11.campaign-...
My personal Twitter: / povilaskorop

[@РоманРоманович-я6з]

Small note: chaining assertion also available in "regular" laravel tests.

[@MarienMupenda]

Thank you for the video, I will finally start writing tests after this series.

[@Denakino]

You can even save 2 more characters per test by using it() instead of test().

You're the best

[@code75581]

Thanks for the video. Please where the $this comes from as there is no class in the file created with --pest flag

[@_KimAngell]

It comes from Illuminate\Foundation\Testing\TestCase, which is extended as an abstract class in ~/tests/TestCase.php

[@coolcha]

Dont know why, but I still prefer phpunit.

[@LaravelDaily]

Me too.

[@coolcha]

@@LaravelDaily I suppose I feel there is too much "magic" happening, like in the config. If I open the test I feel I will not know what all is being loaded in the background by just looking at the test class.

[@maxshaian7260]

My reasons why. 1) Procedural code against OOP. İt makes testing less flexible. I cannot use standard Oop features and have to call different methods to achieve the same. Also no hinting this way. İn particular, laravel standard helpers. 2) Maybe I haven't figured out out, but it's console outputs miss styling, which is hard to read and debug. 3) Tests written with it look less readable for me. I have to check what I call, why and what preparation is made and where. İt's ok for a little number of tests, but for more it is harder. 4) I don't see any advantages before phpunit. Please, guide me if you know. Features like call the same test several times with different inputs looks like a fancier implementation of foreach