About the course

Download all lessons

Lesson summaries

Getting the Ball Rolling

• What Do We Build First?
• Sketching out Our First Test
• Getting to Green
• Unit Testing Presentation Logic
• Refactoring for Speed
• Hiding Unpublished Concerts
• Testing Query Scopes
• Factory States

Purchasing Concert Tickets

• Intro
• Browser Testing vs Endpoint Testing
• Outlining the First Purchasing Test
• Faking the Payment Gateway
• Adding Tickets to Orders
• Encapsulating Relationship Logic in the Model
• Getting Started with Validation Testing
• Reducing Duplication with Custom Assertions
• Handling Failed Charges
• Preventing Ticket Sales to Unpublished Concerts

Limiting Ticket Sales

• Outlining the First Test Case
• Adding Tickets to Concerts
• Refusing Orders When There Are No More Tickets
• Finishing the Feature Test
• Cancelling Failed Orders
• Refactoring and Redundant Test Coverage
• Cleaning Up Our Tests

Returning Order Details

• Asserting Against JSON Responses
• Returning Order Details
• This Design Sucks

A Surgical Refactoring

• Persisting the Order Amount
• Removing the Need to Cancel Orders
• Preparing for Extraction
• Extracting a Named Constructor
• Precomputing the Order Amount
• Uncovering a New Domain Object
• You Might Not Need a Mocking Framework

Off to the Races

• Uh Oh, a Race Condition!
• Requestception
• Hooking into Charges
• Uh Oh, a Segfault!
• Replicating the Failure at the Unit Level
• Reserving Individual Tickets
• Reserved Means Reserved!
• That Guy Stole My Tickets!

Hunting for Stale Code

• Cancelling Reservations
• Refactoring Mocks to Spies
• A Change in Behavior
• Deleting Stale Tests

Something Smells in Our Controller

• Cleaning up a Loose Variable
• Moving the Email to the Reservation
• Refactoring "Long Parameter List" Using "Preserve Whole Object"
• Green with Feature Envy
• Avoiding Service Classes with Method Injection

Testing-Driving the Real Stripe Adapter

• Generating a Valid Payment Token
• Retrieving the Last Charge
• Making a Successful Charge
• Dealing with Lingering State
• Don't Mock What You Don't Own
• Using Groups to Skip Integration Tests
• Handling Invalid Payment Tokens
• The Moment of Truth

Keeping Things Synchronized with Contract Tests

• When Interfaces Aren't Enough
• Refactoring Towards Duplication
• Capturing Charges with Callbacks
• Making the Tests Identical
• Extracting a Contract Test
• Extracting the Failure Case

Upgrading Our Suite to Laravel 5.4

• Upgrading to Laravel 5.4
• Removing the BrowserKit Dependency

Viewing Order Confirmations

• Sketching out Order Confirmations
• Driving out the Endpoint
• Asserting Against View Data
• Extracting a Finder Method
• Making Static Data Real
• Deciding What to Test in a View
• Decoupling Data from Presentation

Generating Confirmation Numbers

• Fixing the Test Suite
• Stubbing the Interface
• Updating Our Unit Tests
• Confirmation Number Characteristics
• Testing the Confirmation Number Format
• Ensuring Uniqueness
• Refactoring to a Facade

Storing the Last Four Card Digits

• Promoting Charges to Objects
• Leveraging Our Contract Tests
• Storing Charge Details with Orders
• Deleting More Stale Code

Assigning Ticket Codes

• Feature Test and JSON Updates
• Claiming Tickets When Creating Orders
• Assigning Codes When Claiming Tickets
• The Birthday Problem
• Integrating Hashids
• Dealing with Out of Sync Mocks
• Wiring It All Together
• Ready to Demo

Emailing Order Confirmations

• Using a Fake to Intercept Email
• Testing Mailable Contents
• Cleanup and Demo

Logging in with Dusk

• Testing the Login Endpoint
• Should You TDD Simple Templates?
• Namespacing Our Test Suite
• Getting Started with Laravel Dusk
• QA Testing the Login Flow

Adding New Concerts

• Preventing Guests from Adding Concerts
• Adding a Valid Concert
• Validation and Redirects
• Converting Empty Strings to Null
• Reducing Noise with Form Factories
• Connecting Promoters to Concerts
• Autopublishing New Concerts

Listing a Promoter's Concerts

• Asserting Against View Objects
• Avoiding Sort-Sensitive Tests
• Refactoring Assertions with Macros

Updating Basic Concert Info

• Viewing the Update Form
• The First Update Test
• Driving Out Basic Concert Updates
• Restricting Updates to Unpublished Concerts

Postponing Ticket Creation

• Storing the Intended Ticket Quantity
• Updating the Other Tests
• Refactoring Away Some Test Duplication
• Creating Tickets at Time of Publish
• Custom Factory Classes

Publishing Concert Drafts

• Discovering a New Resource
• Creating Published Concerts
• Adding Concerts without Publishing
• Pushing Logic Out of the View
• More Custom Assertion Fun

Building the Sales Dashboard

• Calculating Tickets Sold
• Making the Progress Bar Work
• Total Revenue and a Relationship Bug

Listing Recent Orders

• Creating a Custom OrderFactory
• Asserting Against Sort Order
• Splitting Large Tests

Queuing Mass Attendee Emails

• Storing Messages for Attendees
• Confirming That a Job Was Dispatched
• Unit Testing the Job
• Refactoring for Robustness
• Mailable Testing Refresher and Demo

Upgrading to Laravel 5.5

• Upgrading to Laravel 5.5

Uploading Concert Posters

• Faking Uploads and File Systems
• Storing Files and Comparing Content
• Validating Poster Images
• Optional Files and the Null Object Pattern

Optimizing Poster Images

• Testing Events
• Testing the Event Listener
• Resizing the Poster Image
• Optimizing the Image Size

Inviting Promoters and Accepting Invitations

• Upgrading Laravel and Deleting Some Code
• Viewing an Unused Invitation
• Viewing Used or Invalid Invitations
• Registering with a Valid Invitation
• Registering with an Invalid Invitation
• Validating Promoter Registration
• Testing a Console Command
• Sending Promoters an Invitation Email
• Test-Driving the Email Contents

Automating Payouts with Stripe Connect

• Getting Cozy with Stripe Connect
• Authorizing with Stripe
• Exchanging Tokens
• Unit Testing Middleware
• Testing Callbacks with Invokables
• Testing That Middleware Is Applied
• Updating Factories and a Speed Trick
• Total Charges for a Specific Account
• Paying Promoters Directly
• Splitting Payments with Stripe
• It's Alive!