Have you ever had to write an API integration from scratch? Where you’re managing the HTTP calls yourself instead of being able to rely on third-party packages?
You might have used Guzzle to do so or, maybe better, Laravel’s HTTP client.
If you’re using the latter one, you’ll be happy to know that the HTTP facade offers some great testing tools.
Imagine a repository class that can fetch RSS feeds from the web and parse them into a collection of structured data. Maybe something like this:
class RssRepository
{
public function fetch(string $url)
{
$rss = Http::get($url)->body();
return Rss::parse($rss)->map(
fn (array $data)
=> RssEntry::fromArray($data)
);
}
}
Now, you definitely want to test whether your mapping logic works, but you don’t want to send a real HTTP request every time you run your test. That’s where the HTTP fake can help you:
Http::fake([
‘https://test.com/*’
=> Http::response($fakeRssBody),
]);
Notice the * wildcard in the URL? That’s right! The HTTP fake is able to return different responses based on the URL and even supports wildcards! You could even choose to use one wildcard for all requests:
Http::fake([
‘*’ => Http::response($fakeRssBody),
]);
There is a little more to tell about HTTP fakes, sequences for example; but we’ll cover that in our Testing Laravel course.