test: assert the admin panel login flow instead of a 200 on / - #85
Merged
Merged
Conversation
The kit has no '/' route (the panel lives at /admin), so the stock Laravel ExampleTest always got a 404 and the tests CI was red. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The stock Laravel
ExampleTestexpected200on/, but the kit ships no/route (the Filament panel lives at/admin), so the tests CI got a404and was always red.The test now asserts that
/adminredirects guests tofilament.admin.auth.loginand that the login page renders. Passes locally (PHP 8.4, assets built with pnpm).