Jeffrey Way

Musings, thoughts, and brain dumps.

Faster Laravel Tests With…

I released a package months ago, but never really promoted it much. In this five minute video, if you’re interested, let me give you a whirlwind tour of what you can do with it (factories, PHPUnit wrappers, controller/model helpers, etc.) Podcast #2

Earlier this week, I was a guest on the second episode of the podcast. If you’re interested in listening to three guys ramble on about Laravel architecture, testing, and the upcoming conference in Amsterdam, have a listen after the jump.

New Laravel 4 Generator: Pivot

Creating joinable/pivot tables can sometimes be confusing. Should the table names be plural? In what order do we write the table names to make Laravel happy? What fields should be in the pivot table?

I decided to add a pivot table helper generator to my Laravel 4 Generators package. It’s a cinch to use!

“The MVC Mindset” Teaser

My next course for Tuts+ Premium will be released on the final day of July (2013). We have lots of courses that cover beginner-level PHP, and plenty more that focus on object-oriented programming and architecture. But what we didn’t yet have was a course that transitions the developer from messy, muddy procedural code, over to a more structured MVC-based architecture.

Here’s an excerpt from the course: lesson seven.

Download Video

Stay tuned to @tutspremium on Twitter for the official release announcement next week!

AspectMock Is Pretty Neat

I’ve been toying around with a new PHP mocking library, AspectMock (built upon Go! AOP) that takes a different approach - one that doesn’t necessarily require you to resort to dependency injection.

I’ve only spent a matter of hours with this tool, but it just might change the way I structure my projects in the future. I guess we’ll see. Have a watch below and decide for yourself!

Download Video

Testing Laravel Controllers

Testing controllers isn’t the easiest thing in the world. Well, let me rephrase that: testing them is a cinch; what’s difficult, at least at first, is determining what to test.

Should a controller test verify text on the page? Should it touch the database? Should it ensure that variables exist in the view? If this is your first hay-ride, these things can be confusing! Let me help.

Controller tests should verify responses, ensure that the correct database access methods are triggered, and assert that the appropriate instance variables are sent to the view.