Looping Your Unit Tests
When I write my code I like to have my unit tests run automatically but sometimes I need to focus on a single test but I don't want to tab to the window where you're running your unit tests to run them (I know, how lazy can you be). When this happen I like to do two things.
The first is that I can run phpunit in a continuous loop with a one second delay so I can read the screen:
while(true); do vendor/bin/phpunit -c tests --filter <filter>; sleep 1; done
This works well but you end up having the tests run constantly which can drain your battery (if like me you aren't plugged in every so often). In this case I use the following:
while(true); do vendor/bin/phpunit -c tests --filter <filter>; read -p "Press Enter..."; done
Which will wait for an enter key before running the tests a second time.
Scott Keck-Warren
Scott is the Director of Technology at WeCare Connect where he strives to provide solutions for his customers needs. He's the father of two and can be found most weekends working on projects around the house with his loving partner.
Top Posts
- Working With Soft Deletes in Laravel (By Example)
- Fixing CMake was unable to find a build program corresponding to "Unix Makefiles"
- Upgrading to Laravel 8.x
- Get The Count of the Number of Users in an AD Group
- Multiple Vagrant VMs in One Vagrantfile
- Fixing the "this is larger than GitHub's recommended maximum file size of 50.00 MB" error
- Changing the Directory Vagrant Stores the VMs In
- Accepting Android SDK Licenses From The OSX Command Line
- Fixing the 'Target class [config] does not exist' Error
- Using Rectangle to Manage MacOS Windows