From 3d10a41a9fd478bdfedb16493900d35bf80badb5 Mon Sep 17 00:00:00 2001
From: Shift <shift@laravelshift.com>
Date: Mon, 24 Oct 2022 17:29:39 +0000
Subject: [PATCH] Use `<env>` tags for configuration

`<env>` tags have a lower precedence than system environment variables making it easier to overwrite PHPUnit configuration values in additional environments, such a CI.

Review this blog post for more details on configuration precedence when testing Laravel: https://jasonmccreary.me/articles/laravel-testing-configuration-precedence/
---
 phpunit.xml | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/phpunit.xml b/phpunit.xml
index 71c06f5bba..7573685a79 100644
--- a/phpunit.xml
+++ b/phpunit.xml
@@ -33,13 +33,13 @@
     </exclude>
   </groups>
   <php>
-    <server name="APP_ENV" value="testing"/>
-    <server name="BCRYPT_ROUNDS" value="4"/>
-    <server name="CACHE_DRIVER" value="array"/>
-    <server name="MAIL_MAILER" value="array"/>
-    <server name="QUEUE_CONNECTION" value="sync"/>
-    <server name="SESSION_DRIVER" value="array"/>
-    <server name="DB_CONNECTION" value="testing"/>
+    <env name="APP_ENV" value="testing"/>
+    <env name="BCRYPT_ROUNDS" value="4"/>
+    <env name="CACHE_DRIVER" value="array"/>
+    <env name="MAIL_MAILER" value="array"/>
+    <env name="QUEUE_CONNECTION" value="sync"/>
+    <env name="SESSION_DRIVER" value="array"/>
+    <env name="DB_CONNECTION" value="testing"/>
     <const name="PHPUNIT_RUNNING" value="true"/>
   </php>
 </phpunit>