Add env variables to e2e tests to make the tests more portable (bamar…

…ni#114)
PhpDevTools · Jul 10, 2022 · 468af9d · 468af9d
1 parent aa8fa44
commit 468af9d
Show file tree

Hide file tree

Showing 8 changed files with 48 additions and 0 deletions.
diff --git a/e2e/scenario0/script.sh b/e2e/scenario0/script.sh
@@ -2,6 +2,12 @@
 
 set -Eeuo pipefail
 
+# Set env envariables in order to experience a behaviour closer to what happens
+# in the CI locally. It should not hurt to set those in the CI as the CI should
+# contain those values.
+export CI=1
+export COMPOSER_NO_INTERACTION=1
+
 readonly ORIGINAL_WORKING_DIR=$(pwd)
 
 trap "cd ${ORIGINAL_WORKING_DIR}" err exit

diff --git a/e2e/scenario1/script.sh b/e2e/scenario1/script.sh
@@ -2,6 +2,12 @@
 
 set -Eeuo pipefail
 
+# Set env envariables in order to experience a behaviour closer to what happens
+# in the CI locally. It should not hurt to set those in the CI as the CI should
+# contain those values.
+export CI=1
+export COMPOSER_NO_INTERACTION=1
+
 readonly ORIGINAL_WORKING_DIR=$(pwd)
 
 trap "cd ${ORIGINAL_WORKING_DIR}" err exit

diff --git a/e2e/scenario2/script.sh b/e2e/scenario2/script.sh
@@ -2,6 +2,12 @@
 
 set -Eeuo pipefail
 
+# Set env envariables in order to experience a behaviour closer to what happens
+# in the CI locally. It should not hurt to set those in the CI as the CI should
+# contain those values.
+export CI=1
+export COMPOSER_NO_INTERACTION=1
+
 readonly ORIGINAL_WORKING_DIR=$(pwd)
 
 trap "cd ${ORIGINAL_WORKING_DIR}" err exit

diff --git a/e2e/scenario3/script.sh b/e2e/scenario3/script.sh
@@ -2,6 +2,12 @@
 
 set -Eeuo pipefail
 
+# Set env envariables in order to experience a behaviour closer to what happens
+# in the CI locally. It should not hurt to set those in the CI as the CI should
+# contain those values.
+export CI=1
+export COMPOSER_NO_INTERACTION=1
+
 readonly ORIGINAL_WORKING_DIR=$(pwd)
 
 trap "cd ${ORIGINAL_WORKING_DIR}" err exit

diff --git a/e2e/scenario5/script.sh b/e2e/scenario5/script.sh
@@ -2,6 +2,12 @@
 
 set -Eeuo pipefail
 
+# Set env envariables in order to experience a behaviour closer to what happens
+# in the CI locally. It should not hurt to set those in the CI as the CI should
+# contain those values.
+export CI=1
+export COMPOSER_NO_INTERACTION=1
+
 readonly ORIGINAL_WORKING_DIR=$(pwd)
 
 trap "cd ${ORIGINAL_WORKING_DIR}" err exit

diff --git a/e2e/scenario6/script.sh b/e2e/scenario6/script.sh
@@ -2,6 +2,12 @@
 
 set -Eeuo pipefail
 
+# Set env envariables in order to experience a behaviour closer to what happens
+# in the CI locally. It should not hurt to set those in the CI as the CI should
+# contain those values.
+export CI=1
+export COMPOSER_NO_INTERACTION=1
+
 readonly ORIGINAL_WORKING_DIR=$(pwd)
 
 trap "cd ${ORIGINAL_WORKING_DIR}" err exit

diff --git a/e2e/scenario7/script.sh b/e2e/scenario7/script.sh
@@ -2,6 +2,12 @@
 
 set -Eeuo pipefail
 
+# Set env envariables in order to experience a behaviour closer to what happens
+# in the CI locally. It should not hurt to set those in the CI as the CI should
+# contain those values.
+export CI=1
+export COMPOSER_NO_INTERACTION=1
+
 readonly ORIGINAL_WORKING_DIR=$(pwd)
 
 trap "cd ${ORIGINAL_WORKING_DIR}" err exit

diff --git a/e2e/scenario8/script.sh b/e2e/scenario8/script.sh
@@ -2,6 +2,12 @@
 
 set -Eeuo pipefail
 
+# Set env envariables in order to experience a behaviour closer to what happens
+# in the CI locally. It should not hurt to set those in the CI as the CI should
+# contain those values.
+export CI=1
+export COMPOSER_NO_INTERACTION=1
+
 readonly ORIGINAL_WORKING_DIR=$(pwd)
 
 trap "cd ${ORIGINAL_WORKING_DIR}" err exit