Skip to content

Add Pest v4 guidelines #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 6 commits into from
Aug 13, 2025
Merged

Add Pest v4 guidelines #32

merged 6 commits into from
Aug 13, 2025

Conversation

ashleyhindle
Copy link
Collaborator

@ashleyhindle ashleyhindle commented Aug 12, 2025 •
edited
Loading

What & Why

Pest 4 will be out soon and we want people using Boost to get a headstart.

How I tested

  1. Installed Pest 4 into a test project
  2. Ran boost:install
  3. Used claude to ask:
    • "how do pest smoke tests work? What's the code for them? Dont' add one, just tell me" -> search-docs "pest smoke testing" where it showed me the exact code needed
    • "how do i shard my tests?"
    • "Add a browser test for the homepage, click on register, then register with faker() details, and make sure we get redirected to the dashboard"

Notes

  • Should we nudge browser tests to live in tests/Browser/ or no?

Demo

CleanShot 2025-08-12 at 21 07 34@2x

Using Pest docs to write a browser test, then running Pint to make sure the code is okay ❤️
CleanShot 2025-08-12 at 21 08 51@2x
@ashleyhindle ashleyhindle marked this pull request as ready for review August 12, 2025 20:09
@taylorotwell taylorotwell merged commit 82ea478 into main Aug 13, 2025
10 checks passed
@taylorotwell taylorotwell deleted the ai-77-add-pest-v4-guidelines branch August 13, 2025 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants
@ashleyhindle @taylorotwell