Start Writing Laravel Tests That Actually Matter

You're not alone if you've felt this way:

• "I know testing is important, but where do I even begin?"
• "My tests are fragile and break with every small change"
• "Am I even testing the right things?"
• "I've tried learning testing before, but applying it to my real project is... different"

Imagine instead:

• Opening your editor each morning, confident that your test suite has your back
• Making changes to your code without that nagging worry of breaking something
• Having a clear process for what to test in every new feature
• Actually understanding why your tests are written the way they are

A Different Approach to Learning Testing

This isn't another course where you'll build a todo app or a calculator. You'll learn testing principles in your actual project, with real-world complexity and challenges.

Here's How It Works:

1. Each week, watch a short, focused lesson on one key testing principle
2. Then your homework is to apply that principle directly in your project
3. Get support in our private Slack channel if you hit a roadblock
4. At the end of the week, join a live Q&A session where we tackle your specific challenges

What Makes This Workshop Different:

• Learn in Your Project: No toy examples. You'll apply everything you learn in your actual codebase.
• Focused Content: Only what matters, no fluff. Each lesson tackles one specific principle.
• Direct Support: Stuck? Get help in Slack or during our weekly Q&A calls.
• Opinionated Approach: Clear guidelines based on years of real-world testing experience.

Our Track Record

We've helped thousands of developers through our podcast, daily newsletter, and private Slack community.

What You'll Learn

• A repeatable process for identifying what needs testing
• Techniques for testing existing code without getting overwhelmed
• How to write tests that actually give you confidence
• Strategies for testing complex features without diluting the value of your tests

And if you're not already on board with why testing is so valuable, check out these podcast episodes:

• Why do we like testing so much?
• The benefits of testing, even under a deadline

Length of Course:

• Current plan is about 3 - 4 months of weekly lessons
• The weekly Q&A calls will be held for the length of the course
• You will retain access to the videos forever
• You can use the Slack support channel for 6 months (or longer if you are a community member)

Common Questions

Do I need to be a testing expert?
Not at all. If you can write Laravel code, you're ready for this workshop.

What if I use Pest instead of PHPUnit?
The principles we'll cover work with both. We'll use PHPUnit in examples because it helps you understand the fundamentals, but everything translates to Pest.

What kind of projects is this for?
If you're building with Laravel, this is for you. We'll cover testing strategies for traditional apps, APIs, and even console commands.

What if I don't have a project of my own to use?
I will be sharing at least one real-world open source project with limited test coverage that you can use if you prefer.

How much time do I need?
Plan an hour or two per week for course material: watching the lessons, participating in Slack, attending Live Q&A. And at least another 2 - 3 hours to apply the lessons in your own project. (This is where the magic happens!)

When will the Q&A sessions be held?
I will survey the first cohort to find a day/time each that works for most, but it will likely be in the morning US time to allow sufficient overlap with Europe.

What if I can't attend live?
All sessions will be recorded and posted for replay. You can post a question to be answered, even if you can't attend live.

What if I my project is under NDA? How will I get help?
You are under no obligation to share source code when asking for help. If necessary, you can share small sanitized snippets. If it's a very complex issue that requires source code for context, you will need to decide what can be shared or not. Or contact us for pricing on a private, enterprise version of this workshop for your team.

What topics will be covered?

For the beta group, the curriculum will be developed dynamically in response to student needs, but here is a list of some of the currently planned topics

1. Setting up your testing configuration
2. Organizing your test suite consistently
3. What should be in your seeder?
4. Reduce friction to run tests in your editor
5. Setting up factories for better tests
6. Writing your first feature test
7. Adding in authentication and authorization tests
8. How much should I cover in this feature test?
9. What assertions give the most confidence?
10. Do you test middleware?
11. How many tests should I write for this controller action?
12. Consistent names help you organize your test logic
13. Testing API resources
14. Testing create and update methods
15. How should I test validation logic?
16. Testing pagination, filtering, and sorting
17. How much stock should you put in code coverage?
18. What makes code hard to test?
19. Testing events and listeners
20. Testing jobs
21. Testing mail and notifications
22. How to handle external HTTP calls
23. When should I use mocking?
24. Course wrap-up and next steps