Jason

Overview Laravel 11.34 continues the framework's tradition of polishing the developer experience. This release focuses on reducing boilerplate in tests and expanding the utility of the built-in number helpers. By introducing shorthands for HTTP fakes and more descriptive storage assertions, the framework allows you to write cleaner, more readable code that focuses on intent rather than implementation details. Prerequisites To follow this guide, you should have a baseline understanding of the Laravel framework, specifically how to use PHPUnit or Pest for testing. Familiarity with Laravel Facades like `Storage`, `Http`, and `Number` is essential. Key Libraries & Tools - **Laravel 11.34**: The core framework providing these new helpers. - **Storage Facade**: Handles filesystem abstractions and mocking. - **HTTP Facade**: Manages outgoing API requests with powerful testing fakes. - **Number Helper**: A utility class for formatting and manipulating numeric data. Code Walkthrough 1. Simplified Storage Assertions Testing file uploads or generated reports becomes faster with the `assertCount` method. Instead of manually retrieving all files and counting them, you can now verify the state of a disk directly. ```php Storage::fake('photos'); // ... perform logic that saves 3 files ... Storage::disk('photos')->assertCount(3); ``` 2. HTTP Fake Shorthands Previously, faking an HTTP response required wrapping your data in `Http::response()`. Laravel now infers the response type based on the value you provide in the fake array. ```php Http::fake([ 'api.example.com/*' => ['title' => 'My Fake Podcast'], // Auto-resolves to 200 JSON 'api.example.com/error' => 500, // Auto-resolves to status code 'api.example.com/text' => 'Plain text response', // Auto-resolves to string ]); ``` 3. Ordinal Spelling The `Number` helper now includes a `spellOrdinal` method. This combines the logic of converting a number to its ordinal form (1st, 2nd, 3rd) and spelling it out as text. ```php use Illuminate\Support\Number; // Returns "forty-seventh" $result = Number::spellOrdinal(47); ``` Syntax Notes Laravel uses **Type Inference** within the `Http::fake()` method. If the value is an `array`, it assumes a JSON response with a 200 status. If it's an `int`, it treats it as the status code. This removes the need for repetitive Facade calls. Practical Examples - **Leaderboards**: Use `Number::spellOrdinal` to display "You finished in twenty-first place" in a user-friendly UI. - **Data Pipelines**: Use `Storage::assertCount` to ensure a batch process generated exactly the expected number of CSV segments. - **API Integration**: Quickly mock external services by returning raw arrays in your test setup, keeping the "Arrange" section of your tests concise. Tips & Gotchas When using the HTTP shorthands, remember that returning an `int` will result in an empty response body with that status code. If you need a specific body *and* a non-200 status code, you must still use the full `Http::response($body, $status)` syntax to avoid ambiguity.

Overview Laravel 11.21 introduces significant quality-of-life improvements focused on testing ergonomics and database management. These updates refine how developers handle HTTP headers in tests, simplify CLI choice assertions, and provide more expressive ways to verify model existence in the database. By reducing boilerplate, these features keep test suites readable and maintainable. Prerequisites To follow this guide, you should be familiar with the Laravel framework, specifically **PHPUnit** or **Pest** for testing. Understanding Eloquent models and the basics of **Artisan** commands is essential. Key Libraries & Tools - **Laravel 11.21**: The latest framework release featuring these updates. - **Laravel Prompts**: The library powering interactive CLI feedback. - **Eloquent ORM**: The database layer managing soft deletes and model destruction. Code Walkthrough Batch Header Removal Previously, you had to chain multiple `withoutHeader` calls. Now, you can pass an array of headers to be ignored in one go. ```python // Before: Chained methods $response = $this->withoutHeader('X-First')->withoutHeader('X-Second')->get('/'); // Now: Single array call $response = $this->withoutHeaders(['X-First', 'X-Second'])->get('/'); ``` Streamlined DB Assertions Testing for a specific model's presence in the database is now more intuitive. By passing a model instance as the first argument to `assertDatabaseHas`, Laravel automatically infers the table and constraints by the model's primary key. ```python $podcast = Podcast::factory()->create(); // New shorthand: No second argument needed $this->assertDatabaseHas($podcast); ``` Force Destroying Soft Deletes When using soft deletes, the standard `destroy` method merely sets a `deleted_at` timestamp. Laravel 11.21 introduces `forceDestroy` to bypass the soft-delete layer and permanently remove records via the class name. ```python // Permanently removes ID 1, ignoring soft delete logic Podcast::forceDestroy(1); ``` Syntax Notes In the new `expectsChoice` assertion, you can now pass an associative array directly as the options list. This aligns the test syntax with the `select` prompt syntax used in the Laravel Prompts package, making your test code a mirror image of your implementation code. Practical Examples - **Clean CLI Testing**: Use `expectsChoice` with identical option arrays in both your command and your test to ensure user interaction logic is robust. - **Testing Deletion Flows**: Use `forceDestroy` in your cleanup routines or specific administrative tests where a soft delete is insufficient for the test case scenario. Tips & Gotchas Be careful when passing a model to `assertDatabaseHas`. If you provide a model instance but then manually specify different data in the second argument, the data in the second argument will overwrite the constraints inferred from the model. Always ensure the model instance you pass is the exact record you intend to verify.

Overview Laravel continues to refine its developer experience with the release of versions 10.37 and 10.38. These updates focus on reducing boilerplate code in Blade templates and providing more granular control within the testing suite. By introducing more intuitive syntax for session handling and job assertions, the framework empowers developers to write cleaner, more expressive code. Prerequisites To get the most out of these features, you should be comfortable with basic PHP syntax and the Laravel framework. Familiarity with Blade templating, PHPUnit or Pest testing patterns, and the Laravel Service Bus for queued jobs will help you implement these changes effectively. Key Libraries & Tools - **Laravel 10.37/10.38**: The core framework providing these new helpers. - **Blade**: Laravel's powerful templating engine. - **PHPUnit**: The testing framework used to validate route redirections and job chains. Code Walkthrough Simplified Session Display Previously, displaying a flash message required manual checks via the session helper. The new `@session` directive automates this and provides a local `$value` variable. ```php @session('status') <div class="alert alert-success"> {{ $value }} </div> @endsession ``` Improved Route Testing When testing redirects, we often need to specify where a user originated. The `fromRoute` method replaces the generic `from` method, allowing you to use route names instead of hardcoded URLs. ```php $response = $this->actingAs($user) ->fromRoute('news.edit', ['news' => $news]) ->put(route('news.update', $news), $data); $response->assertRedirect(); ``` Asserting Chained Jobs via Closures You can now inspect the specific properties of a chained job using a closure, ensuring that the correct data passes through the queue. ```php Bus::fake(); // Run the logic... Bus::assertChained([ function (ReleasePodcast $job) { return $job->podcastId === 1; } ]); ``` Syntax Notes The `@session` directive is a specialized conditional. It only renders its content if the specified key exists in the session, automatically injecting the value into a scoped `$value` variable. In testing, the `assertValidationError` method now accepts an array of strings, allowing you to verify that multiple validation rules (like `string` and `min:5`) failed simultaneously for a single input field. Tips & Gotchas When using the new closure-based job assertions, always type-hint the job class in the closure signature. This ensures Laravel can correctly match the job in the chain. For the `@session` directive, remember that it specifically looks for flashed data; it won't replace standard persistent session logic for long-term data storage.