The latest articles on DEV Community by Mirko Lorusso (@mloru). https://dev.to/mloru https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F153325%2Feeeb9ae6-069a-4f2b-96ba-653be794f5ca.jpeg https://dev.to/mloru en Mirko Lorusso Sun, 28 May 2023 13:09:53 +0000 https://dev.to/mloru/speed-up-your-laravel-test-suite-c14 https://dev.to/mloru/speed-up-your-laravel-test-suite-c14 <p>If you work with Laravel and TDD, you certainly know how fast your test suite can grow and even take several minutes to run.<br> With the latest versions of Laravel there are a couple of things you can do to speed it up.</p> <h3> Reset your database status only when you need to </h3> <p>Laravel 8 and up include a new <code>LazilyRefreshDatabase</code> trait, which can be used in place of <code>RefreshDatabase</code> to only migrate and seed the database if the previous test changed it.<br> See <a href="https://laracasts.com/series/jeffreys-larabits/episodes/10">this episode of Laracasts</a> for further information.</p> <h3> Use parallel testing </h3> <p>Another thing you can do to improve the running time of your tests is running them in parallel instead of sequentially.<br> <a href="https://github.com/paratestphp/paratest">The paratest composer package</a> will help you with that. <br> Just follow the instructions in the README to install and use it.<br> Quick tip: with parallel testing, every test will run on a different database. Make sure your database user is allowed to create and operate on each of them, setting his permissions accordingly :)</p> <p>Do you have any other suggestion to share about improving the test running time?</p>