jigsaw VS Pest

Also if anyone knows of any third-party templates for Jigsaw, I can't find any except the default blog and docs that they have in their documentation.

https://github.com/tighten/jigsaw/blob/main/src/Jigsaw.php

I also would argue that the majority of code I see in other languages is equally or worse than the example you gave.

You can write terribly in any language, Laravel included.

We have ~8 Laravel apps and roughly 40-50 Jigsaw projects that we keep up to date like this.

Take a look at Jigsaw from Tighten: https://jigsaw.tighten.co

Now, as for what runs the site. It is a static site, using Jigsaw as the framework. Jigsaw uses Laravel’s blade templating. Since one of my goals this year is to learn Laravel, it was the perfect fit for my site. GitHub is where I've decided to store my repos, and Netlify watches for changes to my main branch and rebuilds my site.

Once you're comfortable with PHPUnit (Unit Testing and TDD) the next step is BDD (Behaviour-Driven Development). For this Behat is a good starting point. But my favourite was always Codeception because it has PHPUnit included and does everything (unit tests, functional test, integration tests). The only awkward part ro both of these is installing selenium (at least on windows) Pest is also becoming very popular among the Laravel community, but it will work with anything https://pestphp.com/

These tests are written with PestPHP.

Thank you, I really appreciate it. I tried to cover all my code with tests and also tried my best to write valid readable tests. (Pest made the whole process enjoyable also.)

Testing in Symfony is fairly easy using the Symfony/PHPUnit-bridge package. You’ll write classes containing your tests and run them, no problem. But creating the classes adds a lot of boilerplate code. What if I told you it’s possible to get rid of a lot of boilerplate code and have a nice and elegant way of writing your tests as if you’re writing an English sentence? This is where Pest comes in!”

When building third-party APIs, it’s important to test your code in every runtime scenario you’ve seen or can foresee. For this, a robust and easy to use & maintain testing framework is a must. As PHP developers, we relied heavily on PHPUnit, but we switched over to the Pest Testing Framework, which simplified and reduced our large library of testing code.

2. pestphp/pest

The package is full tested with Pest an elegant PHP Testing Framework. Now I just relesased the version 0.1.4, with full converage (100%).

Try using pest: https://pestphp.com/. Also you’d have to set up a testing environment with it’s own database. For the env file you should just copy you’re existing env (without tokens etc offcourse :p) the documentation says the following: