Back Button Testing

Testing Jargon

There's no two ways about it: terminology in the testing world is incredibly overwhelming. Let's fix that! Bit by bit, we'll break all of these confusing concepts down as best as we can.

8 episodes
1:05:34 hrs
Start Series
    1. Run Time 8:34 Free

      To begin our journey, we'll review unit testing. What exactly does this refer to?

      View the source for this episode on GitHub.

    2. Run Time 9:16

      A mock offers us a useful way to set expecations on messages that should be sent, without actually sending those messages. It sounds confusing, so let's talk about it for a bit.

    3. Run Time 7:04

      A mock allows us to enforce that certain messages are sent to various collaborators. A stub is a bit different. Think of a stub as a stand-in that returns any kind of hard-coded data. "When this method is called, return false." Let's dig into this idea a bit more.

    4. Run Time 4:02

      Don't worry: a dummy is really easy to understand. If a stub offers us a way to return pre-defined values for method calls, then a dummy strips that all away. They're the perfect stand-ins for collaborators that we don't care about.

    5. Run Time 8:06

      As we begin learning about other styles of testing, you'll surely come across the term, "factory." Let's review exactly what that is.

      Once you've finished this episode, be sure to learn more about TestDummy.

    6. Run Time 6:03

      So you're starting to get the hang of what a unit test is, right? Well, let's move up the chain a bit, and focus on integration tests. These provide an excellent way to group components in our system, and verify that they work as expected.

    7. Finally have a basic understanding of TDD? Red, green, refactor? Well, then, how does BDD (Behavior-Driven Development) play into all of this? Well, think of BDD as TDD done right. As you'll find, we're less interested in things like object state, and more concerned with the conversation that takes place.

    8. Don't worry: acceptance tests are fairly easy to understand. They are tests, from the point of the view of the customer. Does the feature, as a whole (meaning, from the outside-in), work as they expected?

You May Also Enjoy...

Here are some additional series that may be up your alley.

Testing The Lifecycle of a New Feature

Want to join me, as I implement a new feature for Laracasts from scratch? Yes? Great! What exactly will we be tackling? Well, I'd like to offer visito...

26:47 mins
Testing Code Katas with PHPSpec

If martial artists use kata as a method for exercise and practice, what might be the equivalent for coders, like us? Well, code katas are short, repea...

2:36:09 hrs
Testing Intuitive Integration Testing

The reality is that, sometimes, you don't require a big testing framework to help orchestrate conversations with the business, design your objects, an...

1:10:11 hrs
Testing Testing Laravel

Given the number of testing tools and resources available to PHP developers, it's no wonder why so many developers feel overwhelmed. In this series, w...

3:53:32 hrs
Laravel Let's Build A Forum with Laravel and TDD

A forum is a deceptively complex thing. Sure, it's made up of threads and replies, but what else might exist as part of a forum? What about profiles,...

19:29:26 hrs