The best source of Laravel training on the web. 2020-05-22T10:29:55-04:00 Jeffrey Way tag:laracasts.com,2020:/feed tag:laracasts.com,2020-05-22:/lessons/what-we-are-building 2020-05-22T09:50:32-04:00

In this series, we'll build a video game app that pulls data from the IGDB API and displays game information such as popular title, coming soon, videos, and screenshots. We'll explore many front-end features with Laravel and other technologies including the HTTP client, Taliwind CSS, Livewire and Alpine.js. View the source code for this episode on GitHub.

tag:laracasts.com,2020-05-21:/lessons/simpler-code-with-usecase-classes 2020-05-21T13:56:15-04:00

It's true that our tests are currently passing, but that doesn't mean the code is perfect. Not by a long stretch. Consider the fact that one of the core abilities of this application is to track stock. And, yet, if we browse the source code, is there a single point of entry we could visit to learn exactly what happens when this tracking takes place? The answer is unfortunately, "not really." What if we could change that by creating a TrackStock use case class that describes the important steps. View the source code for this episode on GitHub.

tag:laracasts.com,2020-05-20:/lessons/notification-testing-and-previewing 2020-05-20T14:33:03-04:00

If the goal is for this Artisan command to run every five minutes, then we should think of a way to notify the user each time an important stock change occurs. For example, if an item was out of stock yesterday, but is now in stock, we should email the user so they can go buy it right away. Let's test out a typical event + listener approach, before adopting use-cases in the following episode. View the source code for this episode on GitHub.

tag:laracasts.com,2020-05-19:/lessons/history-refactoring 2020-05-19T15:05:01-04:00

We're now successfully creating history entries each time the stock is tracked, however, something feels a bit off. Before we move on, let's take a few moments to refactor our code into a shape that makes a bit more sense. View the source code for this episode on GitHub.

tag:laracasts.com,2020-05-19:/lessons/record-product-history 2020-05-19T14:59:39-04:00

It would be useful if we kept a history log for every product. This way, for example, you could chart the price variance for a product over the last six months. Let's knock that out over the next two episodes. View the source code for this episode on GitHub.

tag:laracasts.com,2020-05-15:/lessons/manual-review 2020-05-15T14:35:15-04:00

Amazingly enough, we haven't yet created a local database. However, because our test suite is at green, let's manually try our new Artisan command. According to the tests, when we run php artisan track, it should ping the necessary APIs to update the local status of all stock that we're currently tracking.

tag:laracasts.com,2020-05-15:/lessons/start-a-bug-fix-with-a-test 2020-05-15T14:27:34-04:00

Our tests are currently passing, but there's still a bug in our code. This is usually an indication that you're missing a unit test. In this episode, we'll write a regression test to reproduce the bug, and then fix it. View the source code for this episode on GitHub.

tag:laracasts.com,2020-05-12:/lessons/techniques-for-testing-against-a-real-api 2020-05-12T12:31:58-04:00

So far in this series, we've faked the third-party API. There's no sense in hitting a real API every single time you run your feature tests. However, we do need to ensure that each Client works the way we expect. Let's tag a set of API-specific tests that will assert against real requests sent to the BestBuy API. View the source code for this episode on GitHub.

tag:laracasts.com,2020-05-08:/lessons/fake-it-till-you-make-it 2020-05-08T13:26:08-04:00

Let's write one more test to confirm that, after we check availability, the local stock database is updated to reflect this new information. Once again, we don't want to hit an actual third-party API. Instead, we'll learn how to manually prepare fakes. View the source code for this episode on GitHub.

tag:laracasts.com,2020-05-07:/lessons/different-strategies-for-different-clients 2020-05-07T15:23:46-04:00

Let's begin extracting each retailer client into its own class. As part of this episode, we'll review a variety of object-oriented techniques, including strategies, interfaces, factories, and more. View the source code for this episode on GitHub.

tag:laracasts.com,2020-05-06:/lessons/refactoring-to-database-seeders 2020-05-06T11:59:26-04:00

Before we move on to our next task, let's take a few moments to refactor our tests. We'll extract most of the setup work for our primary test into a custom database seeder class. View the source code for this episode on GitHub.

tag:laracasts.com,2020-05-05:/lessons/how-to-tdd-artisan-commands 2020-05-05T15:10:24-04:00

In this lesson, Christoph Rumpel will show you how to build and test Laravel console commands, using TDD. Laravel provides a number of useful testing assertions that should help us. Follow along as Christoph creates a command to import users from an external API.

tag:laracasts.com,2020-04-30:/lessons/product-tracking 2020-04-30T16:11:42-04:00

Now that we have a basic idea of where we're going, let's write a feature test for the Artisan command that will track all products in our system. View the source code for this episode on GitHub.

tag:laracasts.com,2020-04-29:/lessons/initial-relationships 2020-04-29T18:00:00-04:00

Now that we have a handful of terms in our minds, let's start with a test and flesh out the basic behavior for our application. View the source code for this episode on GitHub.