Generating PHPUnit code coverage for a Laravel project on Homestead

This post assumes you’re familiar with Laravel’s Homestead VM.

Problem

You want to generate PHPUnit code coverage reports and you’re developing on Homestead VM.

Solution

Add a function to the Homestead aliases file

function code_coverage() {
cd code;xon;phpunit --coverage-html ./public/reports/tests;xoff
}change to the code directory

xon/xoff enable/disable xdebug

Generated coverage reports are written to public/reports/tests directory

Re-provision Homestead VM

$vagrant halt

$vagrant up --provision

Add this function to your .zshrc

function code_coverage() {
vagrant ssh -- -t 'bash -ic "code_coverage"'
chrome ./public/reports/tests/index.html
}

This function connects to the Homestead VM and calls the code_coverage function on the VM writing results to …/tests/index.html which we open up in Chrome. That’s it.

Refresh active Chrome tab on bufWrite

I’ve been working with Tailwind CSS in Laravel Blade templates the last few days and it didn’t take long to tire of flipping between Vim and the browser to refresh the page I’m editing.

My first bright idea was throwing the page into an infinite refresh loop with


    <meta http-equiv="refresh" content="5; URL=/">

That got annoying quick so I turned to the web and found this post http://blog.zamith.pt/blog/2014/06/02/autoreload-with-vim. Thank you for sharing Luís.

I’m new to Vim and didn’t follow the FTPlugin approach Luís shared. I use an autocmd instead

augroup RefreshActiveChromeTab
    autocmd!
    autocmd BufWritePost *.blade.php :silent exec "!./reload-active-chrome-tab"
augroup END

The reload-active-chrome-tab script

#!/bin/bash
# All credit to http://blog.zamith.pt/blog/2014/06/02/autoreload-with-vim/

osascript -e 'tell application "Google Chrome" to tell the active tab of its first window to reload'

Save that to the directory you normally start Vim from or use the absolute path to it in the autocmd.