TDD, regression, characterization, acceptance and smoke tests can look identical in a Pest file. What separates them is the reason they were written, and that reason decides how you read them, name them, and whether you can delete them. A field guide with one running example in Pest 5.
Where the cases of an agent eval come from, when a check should be code, a model or a person, and why the outcome of a run matters more than the path the agent took to reach it.
Why an AI agent needs evals before its next prompt or model change, what makes an agent harder to evaluate than a single LLM call, and the task, run and grade loop every eval is built on.
Putting a separate judge in front of an LLM-based CV screener: Laravel Judgment asks Jev whether a CV contains instructions aimed at the machine, and the application decides what to do with the answer.
How to let a model assess free-text refund requests with Laravel Judgment while the application keeps the decision, first on the hosted Jev and then on a self-hosted Laya server.
How a line of hidden text in a CV can steer an LLM-based screener, and the countermeasures from LLM Application Engineering that limit it: separate instructions, checks before and after the call, least privilege and approval gates.
PHP 8.1 introduced the new Fiber class (see the proposed RFC here https://wiki.php.net/rfc/fiber), which allows running coroutines inside your script, i.e. two functions executing simultaneously