- fix warnings in php tests in GitHub Actions

[mtracz]

This pull request includes changes to the configuration files and workflow setup to improve the testing environment and ensure consistency across different environments. The most important changes include updates to the .env.ci file, modifications to the GitHub Actions workflow, and enhancements to the phpunit.xml configuration.

Configuration Updates:

• [.env.ci]: Removed unnecessary environment variables and updated the DB_HOST to use container service from GitHub Actions.

Workflow Modifications:

• .github/workflows/test-and-lint-php.yml:
  • Corrected the file path from env.ci to .env.ci and added test-and-lint-php.yml to the list of files that trigger the workflow.
  • Changed the service label from pgsql to postgres and updated the POSTGRES_DB to toby-test for consistency.
  • Modified the test execution step to copy .env.ci to .env before running tests with colored output.

PHPUnit Configuration Enhancements:

• phpunit.xml:
  • Added attributes to display details on tests that trigger warnings and to fail on warnings.
  • Changed <server> to <env> for environment variables and removed the DB_HOST entry to ensure it uses the correct environment setup.

---

Problem with tests

Actually all php tests are marked as warning due to file_get_contents() exception.

The problem

The problem is missing .env.testing or .env file on GitHub Actions runner during test execution.
Laravel try to load env file defined in APP_ENV (testing by default in phpunit.xml). If this file not exist, it fallback to .env - if this file not exist the result is file_get_contents warning in tests.

The previous command php artisan test --env=ci loaded variables from .env.ci only in php artisan test command, but this command call phpunit binary (in our case) which bootstrap Laravel app again = load env files again.
--env=ci param is not passed to the phpunit command, so phpunit loads environments from phpunit.xml config, where APP_ENV=testing is defined, so Laravel try to load .env.testing then .env then silently fail.

The solution

For local and CI tests we are using phpunit.xml config file, with few predefined variables. This allow us to smoothly run tests in local environment.
In CI environment we need to rename .env.ci to .env to allow Laravel use variables from this file.
DB_HOST for tests will be used from .env in local environment and from .env.ci renamed to .env in CI environment.
The rest variables can stay predefined in phpunit.xml.
In phpunit.xml file we have defined APP_ENV=testing and this file (.env.testing) not exist, so Laravel will fallback to .env and use these variables if they have not been defined in phpunit.xml file.

It's important to understand precedence of loaded environment variables source

1. In app configuration
2. PHPUnit server configuration
3. System environment variables
4. PHPUnit env configuration
5. .env.testing file (or .env.dusk file)
6. .env file

Helpful articles

• https://jasonmccreary.me/articles/laravel-testing-configuration-precedence/
• https://chipperci.com/docs/builds/env/

Similar issues:

• [Bug]: All Feature tests are marked as WARNING when the .env file is missing pestphp/pest#1276
• Warning .env not exist on artisan test laravel/framework#49870