From a9c777c79a9023dd2d4666d9b0573dbf0b09f719 Mon Sep 17 00:00:00 2001 From: nexxo Date: Tue, 28 Jul 2026 02:24:58 +0200 Subject: [PATCH] Rename the SECRETS_KEY page test to match what it actually checks MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It only ever loaded the page and asserted the banner, never a password save — but its name claimed the crash-on-save case, which is exactly the promise that let that bug ship unnoticed once. The test that earns the crash claim is its new neighbour, added for the same finding. --- tests/Feature/Mail/MailSettingsPageTest.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/Feature/Mail/MailSettingsPageTest.php b/tests/Feature/Mail/MailSettingsPageTest.php index 4bae2ee..9eda5d0 100644 --- a/tests/Feature/Mail/MailSettingsPageTest.php +++ b/tests/Feature/Mail/MailSettingsPageTest.php @@ -87,7 +87,7 @@ it('keeps the old password when the field is left empty', function () { expect($box->fresh()->password)->toBe('bleibt'); }); -it('says so when SECRETS_KEY is missing, instead of crashing on the first password', function () { +it('shows the SECRETS_KEY warning on the page', function () { config()->set('admin_access.secrets_key', ''); Livewire::actingAs(User::factory()->operator('Owner')->create())