Use Dependency Injection in Laravel Console Commands

Sep 23, 2017 laravel php testing
This post is more than 18 months old. Since technology changes too rapidly, this content may be out of date (but that's not always the case). Please remember to verify any technical or programming information with the current release.

It’s important to unit test your application code - even your console commands. So many times, I’ve seen people using the Artisan facade inside of console commands to either queue up new commands or call a different command. This makes it more difficult to unit test the application - you have to rely more on fakery (requiring you to reset your application each time then) and/or integration tests.

For example, you might have a large collection of items in an array inside of our RunSomethingCommand class.

public function handle()
{
  foreach ($this->retrieveALot() as $items) {
    Artisan::queue('do-something', ['item_id' => $item->id]);
  }
}

This is decent - you found you have a lot of items that you have to run - so instead of making the console command wait, you’re using the queue. Good for you! However, I just don’t like that Artisan call in there - in my experience, nested Artisan commands get somewhat tricky to test. I also prefer to use dependency injection whenever possible (you may disagree, that’s up to you. Not the point of this entry.)

Instead, you can import the console command contract into your console command using this line:

use Illuminate\Contracts\Console\Kernel;

Now, let’s take a look at our class, a little bit more expanded.

protected $artisan;

public function __construct(Kernel $artisan)
{
  $this->artisan = $artisan;
}

public function handle()
{
  foreach ($this->retrieveALot() as $items) {
    $this-artisan->queue('do-something', ['item_id' => $item->id]);
  }
}

By naming the protected property $artisan we make it easy to read for someone who isn’t exactly certain what’s going on - it’s also a bit of a self-documenting step. But, this way, we can now unit test this console command outside of the actual Laravel ecosystem. We can mock out the injected Kernel contract item and then make sure that each time the queue command gets called, it will have the proper information. We don’t have to ‘catch’ each of those calls or reset our application after this test.

Extra note - since this is the kernel contract, you could also call items immediately, by using $this->artisan->call() instead of queue().

Looking for more Laravel Tips & Tricks? Join Joel and I on the No Compromises bi-weekly podcast; around 15 minutes of thoughtful real-world advice and helpful info.
Go to All Posts