Unit tests should run in a specified timezone

[carstingaxion]

Describe the bug

Otherwise the created wp-env instance seems to take the OS settings, which will lead to some failing tests, if ran outside of GMT.

1) GatherPress\Tests\Core\Test_Event::test_get_display_datetime with data set #0 (array('2020-05-11 15:00:00', '2020-05-11 17:00:00'), 'Monday, May 11, 2020 3:00 PM ...T+0000')
Failed to assert display date times match.
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'Monday, May 11, 2020 3:00 PM to 5:00 PM GMT+0000'
+'Monday, May 11, 2020 3:00 PM to 5:00 PM CEST'

/var/www/html/wp-content/plugins/gatherpress/test/unit/php/includes/core/classes/class-test-event.php:119

2) GatherPress\Tests\Core\Test_Event::test_get_datetime
Failed asserting that two arrays are identical.
--- Expected
+++ Actual
@@ @@
     'datetime_start_gmt' => ''
     'datetime_end' => ''
     'datetime_end_gmt' => ''
-    'timezone' => '+00:00'
+    'timezone' => 'Europe/Berlin'
 )

Steps to Reproduce

npm run test:unit:php

Screenshots, screen recording, code snippet

No response

Environment information

No response

WordPress information

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[carstingaxion]

This is so annoying, I keep getting different test results, when running locally and compared to when the workflow runs.

Just calling date_default_timezone_set() is heavily discouraged in combination with WordPress, but what to do alternatively?

[carstingaxion]

https://github.com/WordPress/gutenberg/tree/HEAD/packages/env#advanced-php-settings + https://www.php.net/manual/de/datetime.configuration.php#ini.date.timezone = ???

[carstingaxion]

npm run wp-env destroy
npm run wp-env start

helped to solve this (for now). Not sure, if this should need to be prepared better. I'm fine now.