@ervan Hmmm. I'd also make sure you don't have order-dependent tests, share file objects, or run specs that mutate your #database (including #PStore with ultra-safe locking) outside of a #DBtransaction you can abandon.

This is less about making the tests parallel or concurrent than about whether you're using #testfixtures that create #Heisenbugs. Using #testfactories, #tempfiles, or an #MVCC #DB could help you a lot there.

🚀 Laravel's DB::transaction provides robust control over database transactions. Safely perform data-modifying #SQL queries and rollback if needed. This ensures data integrity, especially when creating related entities like an account and a user simultaneously. For advanced control, manually call beginTransaction, rollback, and commit to handle exceptions as needed. 🛠️ #Laravel #DBtransaction

Examples: https://laraveldaily.com/post/laravel-database-transactions-examples

Laravel Database Transactions: 3 Practical Examples

Laravel Daily